2:54 p.m.
I last updated:
Mar 27 01:01:34 INFO Upgraded: icoutils-0.31.3-1.fc24.x86_64
Mar 27 01:01:35 INFO Cleanup: icoutils-0.31.2-1.fc24.x86_64
Since then, dnf update aborts with:
*** Error in `/usr/bin/python3': realloc(): invalid next size:
0x00005597a7b29670 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x7570b)[0x7f66a367e70b]
/lib64/libc.so.6(+0x8080c)[0x7f66a368980c]
/lib64/libc.so.6(realloc+0x184)[0x7f66a368a714]
/lib64/libsolv.so.0(solv_realloc+0x1e)[0x7f6693c2e21e]
/lib64/libsolv.so.0(+0x40cfb)[0x7f6693c2dcfb]
/lib64/libsolv.so.0(+0x33bea)[0x7f6693c20bea]
/lib64/libsolv.so.0(dataiterator_step+0x1161)[0x7f6693c292e1]
/lib64/libhawkey.so.2(+0xf5c4)[0x7f6693e835c4]
/lib64/libhawkey.so.2(hy_query_apply+0x10a3)[0x7f6693e84bf3]
/lib64/libhawkey.so.2(hy_query_run_set+0x9)[0x7f6693e85ef9]
/lib64/libhawkey.so.2(running_kernel+0xac)[0x7f6693e8131c]
/lib64/libhawkey.so.2(sack_running_kernel+0x17)[0x7f6693e870e7]
/lib64/libhawkey.so.2(hy_goal_run_all_flags+0x4bc)[0x7f6693e7f81c]
/usr/lib64/python3.5/site-packages/hawkey/_hawkey.so(+0xa84e)[0x7f669409c84e]
/lib64/libpython3.5m.so.1.0(PyCFunction_Call+0xe9)[0x7f66a43a4f29]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x75b9)[0x7f66a441c759]
/lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x5f59)[0x7f66a441b0f9]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4]
/lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x5f59)[0x7f66a441b0f9]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x7c44)[0x7f66a441cde4]
/lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3]
/lib64/libpython3.5m.so.1.0(PyEval_EvalFrameEx+0x5f59)[0x7f66a441b0f9]
/lib64/libpython3.5m.so.1.0(+0x1279d3)[0x7f66a441e9d3]
/lib64/libpython3.5m.so.1.0(PyEval_EvalCodeEx+0x23)[0x7f66a441eab3]
/lib64/libpython3.5m.so.1.0(PyEval_EvalCode+0x1b)[0x7f66a441eadb]
/lib64/libpython3.5m.so.1.0(+0x146d64)[0x7f66a443dd64]
/lib64/libpython3.5m.so.1.0(PyRun_FileExFlags+0x95)[0x7f66a44402b5]
/lib64/libpython3.5m.so.1.0(PyRun_SimpleFileExFlags+0xf4)[0x7f66a4440424]
/lib64/libpython3.5m.so.1.0(Py_Main+0xedc)[0x7f66a445708c]
/usr/bin/python3(main+0x170)[0x5597a3886b70]
/lib64/libc.so.6(__libc_start_main+0xf1)[0x7f66a3629731]
/usr/bin/python3(_start+0x29)[0x5597a3886c19]
Anyone else seeing this?
--
Kevin J. Cummings
kjchome(a)verizon.net
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)
5:26 p.m.
On Mon, 27 Mar 2017 15:54:42 -0400
Kevin Cummings <cummings(a)kjchome.homeip.net> wrote:
I last updated:
Mar 27 01:01:34 INFO Upgraded: icoutils-0.31.3-1.fc24.x86_64
Mar 27 01:01:35 INFO Cleanup: icoutils-0.31.2-1.fc24.x86_64
URL : http://www.nongnu.org/icoutils/
Summary : Utility for extracting and converting Microsoft icon and cursor files
Description :
The icoutils are a set of programs for extracting and converting images in
Microsoft Windows icon and cursor files. These files usually have the
extension .ico or .cur, but they can also be embedded in executables or
libraries.
Since then, dnf update aborts with:
> *** Error in `/usr/bin/python3': realloc(): invalid next size:
> 0x00005597a7b29670 *** ======= Backtrace: =========
That's a very large size, so it is obviously wrong.
Anyone else seeing this?
No, and my F25 system updated just fine today. It seems crazy that
icoutils would cause a problem in python3 / dnf. Is there any chance
that your disks or memory are going flaky?
You could try downgrading to the previous version of the dnf packages
to see if it is a dnf error. You would probably have to go to koji
https://koji.fedoraproject.org/koji/packageinfo?packageID=14310
to get them at this point. To see what packages you need, do a
dnf remove dnf
and make sure to hit NO. Look at the dependencies that would be erased,
and get all those packages from koji.
Or, just try a reinstall of dnf (and its dependent packages) to see if
that fixes the problem.
5:01 p.m.
On 03/27/17 18:26, stan wrote:
On Mon, 27 Mar 2017 15:54:42 -0400
Kevin Cummings <cummings(a)kjchome.homeip.net> wrote:
> I last updated:
>
> Mar 27 01:01:34 INFO Upgraded: icoutils-0.31.3-1.fc24.x86_64
> Mar 27 01:01:35 INFO Cleanup: icoutils-0.31.2-1.fc24.x86_64
URL : http://www.nongnu.org/icoutils/
Summary : Utility for extracting and converting Microsoft icon and cursor files
Description :
The icoutils are a set of programs for extracting and converting images in
Microsoft Windows icon and cursor files. These files usually have the
extension .ico or .cur, but they can also be embedded in executables or
libraries.
> Since then, dnf update aborts with:
>
>> *** Error in `/usr/bin/python3': realloc(): invalid next size:
>> 0x00005597a7b29670 *** ======= Backtrace: =========
That's a very large size, so it is obviously wrong.
> Anyone else seeing this?
No, and my F25 system updated just fine today. It seems crazy that
icoutils would cause a problem in python3 / dnf. Is there any chance
that your disks or memory are going flaky?
That's a possibility. I have a lot of problems with firefox,
thunderbird, and sometimes parts of the kernel occasionally aborting
because "something went wrong, restarting".
You could try downgrading to the previous version of the dnf
packages
to see if it is a dnf error. You would probably have to go to koji
https://koji.fedoraproject.org/koji/packageinfo?packageID=14310
to get them at this point. To see what packages you need, do a
dnf remove dnf
and make sure to hit NO. Look at the dependencies that would be erased,
and get all those packages from koji.
I had a different solution. I went off site today (w/laptop) and things
worked well where I was. When I got back home, I un-suspended the
laptop but forgot to plug it in. After 2 hours, the battery discharged.
After plugging back in, when I tried to reboot
(kernel-4.9.13-101.fc24), it hung twice trying to start the gui. When I
rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf update
succeeded! Gee, now I have 4.9.17 kernel to try! B^)
Or, just try a reinstall of dnf (and its dependent packages) to see
if
that fixes the problem.
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
--
Kevin J. Cummings
kjchome(a)verizon.net
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)
9:11 a.m.
On Wed, 29 Mar 2017 18:01:29 -0400
Kevin Cummings <cummings(a)kjchome.homeip.net> wrote:
I had a different solution. I went off site today (w/laptop) and
things worked well where I was. When I got back home, I un-suspended
the laptop but forgot to plug it in. After 2 hours, the battery
discharged. After plugging back in, when I tried to reboot
(kernel-4.9.13-101.fc24), it hung twice trying to start the gui.
When I rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf
update succeeded! Gee, now I have 4.9.17 kernel to try! B^)
That makes it sound like the power supply has something to do with your
problems. Maybe it is overheating, or the voltages it provides are
marginal? Could there be a lot of dust buildup in the case?
9:24 a.m.
On Thu, Mar 30, 2017 at 8:11 AM, stan <stanl-fedorauser(a)vfemail.net> wrote:
On Wed, 29 Mar 2017 18:01:29 -0400
Kevin Cummings <cummings(a)kjchome.homeip.net> wrote:
> I had a different solution. I went off site today (w/laptop) and
> things worked well where I was. When I got back home, I un-suspended
> the laptop but forgot to plug it in. After 2 hours, the battery
> discharged. After plugging back in, when I tried to reboot
> (kernel-4.9.13-101.fc24), it hung twice trying to start the gui.
> When I rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf
> update succeeded! Gee, now I have 4.9.17 kernel to try! B^)
That makes it sound like the power supply has something to do with your
problems. Maybe it is overheating, or the voltages it provides are
marginal? Could there be a lot of dust buildup in the case?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Never a bad idea to take an air compressor to a laptop.. or desktop or any
pc for that matter.
11:20 a.m.
On 03/30/17 10:24, InvalidPath wrote:
On Thu, Mar 30, 2017 at 8:11 AM, stan <stanl-fedorauser(a)vfemail.net
<mailto:stanl-fedorauser@vfemail.net>> wrote:
On Wed, 29 Mar 2017 18:01:29 -0400
Kevin Cummings <cummings(a)kjchome.homeip.net
<mailto:cummings@kjchome.homeip.net>> wrote:
> I had a different solution. I went off site today (w/laptop) and
> things worked well where I was. When I got back home, I un-suspended
> the laptop but forgot to plug it in. After 2 hours, the battery
> discharged. After plugging back in, when I tried to reboot
> (kernel-4.9.13-101.fc24), it hung twice trying to start the gui.
> When I rebooted with kernel-4.9.13-100.fc24, it came up, and the dnf
> update succeeded! Gee, now I have 4.9.17 kernel to try! B^)
That makes it sound like the power supply has something to do with your
problems. Maybe it is overheating, or the voltages it provides are
marginal? Could there be a lot of dust buildup in the case?
_______________________________________________
users mailing list -- users(a)lists.fedoraproject.org
<mailto:users@lists.fedoraproject.org>
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
<mailto:users-leave@lists.fedoraproject.org>
Never a bad idea to take an air compressor to a laptop.. or desktop or
any pc for that matter.
Yeah, it has been a while since I "popped the cover" on the laptop....
--
Kevin J. Cummings
kjchome(a)verizon.net
cummings(a)kjchome.homeip.net
cummings(a)kjc386.framingham.ma.us
Registered Linux User #1232 (http://www.linuxcounter.net/)
8:37 p.m.
Allegedly, on or about 30 March 2017, InvalidPath sent:
Never a bad idea to take an air compressor to a laptop.. or desktop
or
any pc for that matter.
It can be if you're not careful, there are risks.
Air blasting out can generate damaging static electricity.
You can blast dust into the bearings of fans.
You can physically damage components with the force of the air (if it's
strong enough, and you get too close).
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
When it comes to electronics, I'm slightly biased.
2576
days inactive
2580
days old
6 comments
4 participants
participants (4)
-
InvalidPath -
Kevin Cummings -
stan -
Tim