[Bug 1898383] [NEW] tcsh filename pattern matching fails
Public bug reported: TCSH filename pattern matching bug -- To reproduce: 1) Make a subdirectory 2) cd to that subdirectory 3) create or touch the files x1 x2 x3 x4 x5 x6 x7 x8 and x9 4) execute the command: "echo x[7-9]" You will see all the files echo, NOT just x7 x8 and x9... /bin/sh and /bin/bash still do this correctly... but tcsh seems broken! Description:Ubuntu 20.04.1 LTS Release:20.04 tcsh: Installed: 6.21.00-1 Candidate: 6.21.00-1 Version table: *** 6.21.00-1 500 500 http://archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: tcsh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898383 Title: tcsh filename pattern matching fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcsh/+bug/1898383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
On 6/10/20 5:48 PM, Henrique de Moraes Holschuh wrote: > This has been reported to be fixed on very similar processors (with the > same microcode signature as yours) in the 20200609 microcode updates, > could you test them? > I see four versions on your webpage: two versions of 3.20200609.0ubuntu0.16.04.1 and two versions of 3.20200609.0ubuntu0.16.04.0. I downloaded all four and both versions of 3.20200609.0ubuntu0.16.04.1 compared without any differences AND both versions of 3.20200609.0ubuntu0.16.04.0 compared without any differences. So in spite of the statement on the web page that each of those versions had a different publishing time, the two versions of .1 seem to be the same and the two versions of .0 seem to be the same. So I tried BOTH versions and warm reboots DID work with either .0 or .1. I left my machine with 3.20200609.0ubuntu0.16.04.1 Let me know if I missed any version you wished me to test... Harry McGavran -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
I finally got a little time to try to search for which package exactly causes this problem. I downloaded: intel-microcode_3.20151106.1_amd64.deb intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb intel-microcode_3.20191115.1ubuntu0.16.04.1_amd64.deb intel-microcode_3.20191115.1ubuntu0.16.04.2_amd64.deb I had downgraded to 3.20151106.1, which is working. So, I tried intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb, and it worked ok. So, next I tried intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb, and it worked ok. So, Next I tried intel-microcode_3.20191115.1ubuntu0.16.04.1_amd64.deb and it hangs on warm reboot. So, next I tried intel-microcode_3.20191112-0ubuntu0.16.04.2_amd64.deb, and NOW IT hangs on warm reboot. So, next I tried intel-microcode_3.20190618.0ubuntu0.16.04.1_amd64.deb, and now IT TOO hangs on warm reboot. So, Next I tried intel-microcode_3.20151106.1_amd64.deb, and it works ok -- Unfortunately, I just don't have time to go back one by one through all the releases between 3.20151106.1 and 3.20190618.0 to see how far back I need to go before finding where it really would start working ok again. I find it very puzzling that the packages all worked until I got to 3.20191115.1ubuntu0.16.04.1, and then none of them worked until I backed off all the way to 3.20151106.1. There must be a clue in that somewhere. Good luck, I hope you find it -- I'm staying locked on 3.20151106.1 until this gets fixed... Harry On 12/17/19 12:51 PM, Harry G McGavran Jr wrote: > > > On 12/17/19 12:13 PM, Harry G McGavran Jr wrote: >> >> >> On 12/17/19 11:52 AM, Seth Arnold wrote: >>> Hello Harry, >>> >>> Just to double-check, did you perform a *cold* reboot at least once >>> after installing the 3.20191115.1ubuntu0.16.04.2? > > Meant to respond to this in my first reply... > > The answer to this one is yes. > > The only way I could get the system to come up was with a cold boot as > well. This was true for each of the last two microcode releases > in my update stream. > > Harry > > >>> >>> Can you please provide the output of: >>> >>> iucode-tool -S >> >> iucode-tool: system has processor(s) with signature 0x00050654 >> >>> >>> It might also be helpful to know where exactly the failure started; >>> previous releases can be found on >>> https://launchpad.net/ubuntu/xenial/+source/intel-microcode >>> >>> (I'm guessing it's probably fastest to just work backwards up the list >>> rather than bisecting, but that's a guess.) >> >> I believe it was a problem with the last two microcode releases for >> Ubuntu 16.04 LTS. >> >> That would be the 3.20191115 and 3.20191112 releases. >> The 3.20190618 releases and before were ok. >> >> Exactly which ones on 3.20191115 and 3.20191112, I don't >> know without trying them, but the ones in the update stream >> for Ubuntu 16.04 LTS are the ones where I had trouble. >> >>Harry >> >>> >>> Here's the previous bug report for a handy link for navigating among the >>> bugs: >>> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764 >>> >>> Thanks >>> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
On 12/17/19 12:13 PM, Harry G McGavran Jr wrote: > > > On 12/17/19 11:52 AM, Seth Arnold wrote: >> Hello Harry, >> >> Just to double-check, did you perform a *cold* reboot at least once >> after installing the 3.20191115.1ubuntu0.16.04.2? Meant to respond to this in my first reply... The answer to this one is yes. The only way I could get the system to come up was with a cold boot as well. This was true for each of the last two microcode releases in my update stream. Harry >> >> Can you please provide the output of: >> >> iucode-tool -S > > iucode-tool: system has processor(s) with signature 0x00050654 > >> >> It might also be helpful to know where exactly the failure started; >> previous releases can be found on >> https://launchpad.net/ubuntu/xenial/+source/intel-microcode >> >> (I'm guessing it's probably fastest to just work backwards up the list >> rather than bisecting, but that's a guess.) > > I believe it was a problem with the last two microcode releases for > Ubuntu 16.04 LTS. > > That would be the 3.20191115 and 3.20191112 releases. > The 3.20190618 releases and before were ok. > > Exactly which ones on 3.20191115 and 3.20191112, I don't > know without trying them, but the ones in the update stream > for Ubuntu 16.04 LTS are the ones where I had trouble. > >Harry > >> >> Here's the previous bug report for a handy link for navigating among the >> bugs: >> https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764 >> >> Thanks >> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1855784] Re: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
On 12/17/19 11:52 AM, Seth Arnold wrote: > Hello Harry, > > Just to double-check, did you perform a *cold* reboot at least once > after installing the 3.20191115.1ubuntu0.16.04.2? > > Can you please provide the output of: > > iucode-tool -S iucode-tool: system has processor(s) with signature 0x00050654 > > It might also be helpful to know where exactly the failure started; > previous releases can be found on > https://launchpad.net/ubuntu/xenial/+source/intel-microcode > > (I'm guessing it's probably fastest to just work backwards up the list > rather than bisecting, but that's a guess.) I believe it was a problem with the last two microcode releases for Ubuntu 16.04 LTS. That would be the 3.20191115 and 3.20191112 releases. The 3.20190618 releases and before were ok. Exactly which ones on 3.20191115 and 3.20191112, I don't know without trying them, but the ones in the update stream for Ubuntu 16.04 LTS are the ones where I had trouble. Harry > > Here's the previous bug report for a handy link for navigating among the bugs: > https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1854764 > > Thanks > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855784] [NEW] Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi
Public bug reported: Intel Micorocde 3.20191115.1ubuntu0.16.04.2 STILL hangs on warm reboot with Dell T5820 and Intel(R) Xeon(R) W-2125 CPU Reverting to 3.20151106.1 fixes the problem. Running Ubuntu 16.04 LTS. ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855784 Title: Intel Microcode 3.20191115.1ubuntu0.16.04.2 still hangs on warm reboot with Intel(R) Xeon(R) W-2125 CPUi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1855784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
I haven't been able to find how to set a tag for my post above (#10). It should have the "verification-done-xenial" tag. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829813] Re: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu
I just installed proposed fwupd 0.8.3 on Xenial. The "Mismatched XML" issue disappeared, fwupdmgr found new firmware. I updated the firmware and everything seems to work fine. Running fwupdmgr after this process and rebooting seems fine too, no "Mismatched XML" With the previous version, the "Mismatched XML" issue didn't always happen, but it's been happening the past week or thereabouts. If this problem returns, I'll post any issues here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829813 Title: fwupdmgr refresh shows "Mismatched XML" error in 16.04 Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1829813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 762025] Re: acroread package from canonical reports errors on amd64 systems
This is a good lead as to where some more ia32-libs bugs are!! It turns out what I needed to do for lucid to achieve the same thing in lucid that you outlined with natty was: /usr/bin/gdk-pixbuf-query-loaders /etc/gtk-2.0/gdk-pixbuf.loaders.32 /bin/sed -i -e 's#/usr/lib#/usr/lib32#' /etc/gtk-2.0/gdk-pixbuf.loaders.32 /usr/bin/gtk-query-immodules-2.0 /etc/gtk-2.0/gtk.immodules.32 /bin/sed -i -e 's#/usr/lib#/usr/lib32#' /etc/gtk-2.0/gtk.immodules.32 Thanks! I wish Ubuntu would support it's LTS stuff better -- this is the second area I've needed to patch. Another was reported in launchpad by das3rd: The workaround was to do the following sudo ln -s /usr/lib32 /usr/123 sudo sed -i -e 's/usr\/lib/usr\/123/g' libgio-2.0.so.0.2400.1 to patch libgio, THEN get a copy of libgvfscommon.so.0.0.0 from a 32 bit system and copy it into /usr/lib32, fix permissions, owner and add a symlink sudo chown root libgvfscommon.so.0.0.0 sudo chgrp root libgvfscommon.so.0.0.0 sudo chmod 644 libgvfscommon.so.0.0.0 sudo ln -s libgvfscommon.so.0.0.0 libgvfscommon.so.0 and Scott Ritchie fixed it in Maverick -- but NOT Lucid! I don't understand why this stuff doesn't get fixed in the LTS release! Thanks again for the lead! Harry On Thu, 23 Jun 2011 14:12:44 - jason hord wrote: The following worked around the issue on natty (11.04) for me: sudo sh -c 'sed s#/usr/lib/#/usr/lib32/#g /usr/lib/gdk- pixbuf-2.0/2.10.0/loaders.cache /usr/lib/gdk- pixbuf-2.0/2.10.0/loaders.cache.32' A similar fix might be possible for older distributions. -- = You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/762025 Title: acroread package from canonical reports errors on amd64 systems Status in =E2=80=9Cacroread=E2=80=9D package in Ubuntu: New Bug description: Binary package hint: acroread Apparently only on 64 bit systems, the acroread package from canonical re= ports a number of errors like: (acroread:25310): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion = `GDK_IS_PIXBUF (pixbuf)' failed (acroread:25310): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion= `GDK_IS_PIXBUF (pixbuf)' failed (acroread:25310): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_= IS_OBJECT (object)' failed (acroread:25310): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_= IS_OBJECT (object)' failed etc. etc. acroread still runs, but seeing these errors reported all the time is a bug. Surfing about other apps with similar problems implies that the problem is a bug in the lib32 stuff for 64 bit systems. It was fine in Hardy, but b= roken in Lucid. So, it's likely a lib32 problem for 64 bit systems instead of an acroread= problem. lsb_release -rd Description:Ubuntu 10.04.2 LTS Release:10.04 apt-cache policy acroread acroread: Installed: 9.4.2-0lucid1 Candidate: 9.4.2-0lucid1 Version table: *** 9.4.2-0lucid1 0 500 http://archive.canonical.com/ubuntu/ lucid/partner Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/762025/+subscriptio= ns -- Harry G. McGavran, Jr. E-mail: w5...@w5pny.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762025 Title: acroread package from canonical reports errors on amd64 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acroread/+bug/762025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619293] Re: ia32-libs requires libgvfscommon0 for gvfs
I'm really tired of Ubuntu not fixing bugs like this in an LTS release. I'm running Lucid and finally did the above work-around too. Still no fix for lib32 on amd64 Lucid from Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/619293 Title: ia32-libs requires libgvfscommon0 for gvfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ia32-libs/+bug/619293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762025] Re: acroread package from canonical reports errors on amd64 systems
I now have 32 bit Lucid installed on my T61P Thinkpad, and the acroread binary seems the same as the one on my 64 bit Lucid, BUT the 32 bit system does NOT have the problem! This is in spite of the fact that there is only the 2.10.0 lib directory on the 32 bit system as well and no 2.4.0 directory. So it looks to me like a lib32 package problem on 64 bit Lucid. Is anyone who can fix the lib32 package on Lucid reading this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762025 Title: acroread package from canonical reports errors on amd64 systems -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
