Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
Package: eterm Version: 0.9.6-1 Followup-For: Bug #737491 Dear Maintainer, Since updating my machine from Wheezy to Jessie, Eterm now uses 100% CPU when started. I've tried starting Eterm manually with no command line arguments and it never gets as far as displaying a bash prompt. I'm not really sure how to debug this further; please let me know anything I can do to find out more information. Thanks for your help. -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-0.bpo.2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages eterm depends on: ii libast20.7-7 ii libc6 2.19-18+deb8u7 ii libfreetype6 2.5.2-3+deb8u1 ii libice62:1.0.9-1+b1 ii libimlib2 1.4.6-2+deb8u2 ii libsm6 2:1.2.2-1+b1 ii libx11-6 2:1.6.2-3 ii libxext6 2:1.3.3-1 ii multiarch-support 2.19-18+deb8u7 ii zlib1g 1:1.2.8.dfsg-2+b1 eterm recommends no packages. eterm suggests no packages. -- no debconf information
Bug#770369: Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
Hi, Thanks for your help! I think this bug is the same than bug #770369. I tried to file this as a followup to the existing bug but must have messed up with my usage of `reportbug`; sorry! This bug is close in stretch (testing). As it is expected the release stretch occurs soon, the easiest way is: 1. To wait for the release of stretch to get this problem fixed when you upgrade from Wheezy to Stretch. 2. Downgrade the Eterm package to the version in Jessie so you can use it until the upgrade to Stretch. Do you mean wheezy? Do you have a command to hand that can do that for me or is it best to fetch the .deb out of the appropriate package pool? I am trying to maintain Eterm package, but my process of learning to do it properly is getting a little long so I have not prepared a new Eterm package. I have checked the fix proposed and my local Eterm package is working in Jessie-amd64 (thanks to Charles Gorand and Arnaud Ceyroll for the fix). Andy, if you want I can send you my local package to your e-mail, so you can use it. For Santiago Vila (or other developers) I have modified the source package in Jessie by performing the fix suggested by Arnaud and Charles to the command.c file, just recompiled in my Jessie system and the new Eterm package is working again. Maybe I can try to build my own local package? Are you able to send me the patch for the Jessie package? Maybe it is worth to propose an update for Jessie so the package will be usable again for all the users. I will have some spare time after the middle of June, so I would be able to apply the fix in the correct way (I have just edited the source to test it, I have to read deeper the maint-guide to do it in the right way). After the release of Stretch I will try to fix the UTF8 problem in Eterm to finally maintain this package. Thanks for your help and for giving the time. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF
Bug#737491: eterm: Occurs on upgrade to Jessie from Wheezy
Hi, Andy, I have tested a couple of solutions and I think the easiest way for you is just to download the Eterm package for Stretch (testing) and install it in your system manually with: dpkg -i eterm_0.9.6-4_amd64.deb I have just installed the Eterm version in testing and no new packages are needed, just this one and it is working in my system. (One can use pinning in apt to install packages for several distributions, but for just one package I think it is not necessary in this case). Please, let me know if this solution is not working for you to try a more elaborate fix until Stretch is released. That works great, thanks! Thank you so much for your help; it's been really generous of you. Regards, @ndy -- andy...@ashurst.eu.org http://www.ashurst.eu.org/ 0x7EBA75FF
