[arch-general] did my 4/10/10:pacman -Syu: destabilized e17's run command dialog??
Actually, I'm not sure if this is thanks to E17 itself or specific to Arch... And it's no big deal anyway because: A) e17 is "under heavy development", (And I know that means it's unstable) B) I've already got a workaround that works for me... But I'd like to understand what happened a little better. First you should know that I'm a multi-Linux/multi-boot kind of guy, and that in every distro I install I depend on their package management system to keep me out of dependency hel^Hck... ;-7 Of all my currently installed distros, Arch is the one that seems most likely to install an unadulterated upstream package, rather than a distro specific {modified} version. And e17 is definitely a "package" that I wouldn't even attempt to install by hand. Thus the fact that the only e17 on my laptop that this has happened to is the one in Arch, doesn't make it distro specific. It probably only means the Arch e17 is more fully updated... At least that's mt best guess. Anyway I'm not sure what the e17 version number that I installed to Arch sometime since my mid March initial installation of Arch itself was, but as of now the e17 help about lists it as "Enlightenment 0.16.999.063". Prior to this recent pacman -Syu, e17's run prompt worked normally. Afterwards it's become fussy what the first character I input into it is. That is I usually start opera via the run prompt and when I type "o" the command history displays the last instance of the command And I can in fact start opera. I also use firefox, though I usually start that from inside alpine. Today I tried to start firefox from the run prompt. But as soon as I type an "f" into the first character position of the command input field, I get a pop-up error telling me that "Enlightenment SEGV'd" That also advises me to compile everything with "-g in CFLAGS" So far, the the restore button succeeds in restarting e17 without closing any open applications... But of course I didn't get firefox. I can start firefox from an xterm. And I tested that I can type "of" into the run prompt without an immediate SEGV But I can't type an f as the first character. I haven't tested the whole alphabet, But I also can't type a command starting with "b" or "/" as the first character. Though just because I'm stubborn I can tell you that I can start firefox [via e17's run prompt] with: "~/../../usr/bin/firefox" (go figure) I did say I've got a work around that works for me... I've also got XFCE installed as a back-up desktop, so I've reassigned the keybinding I used to pull up e17's run prompt with, to "/usr/bin/xfrun4". Which is works just fine. How can I a regular "Joe user", figure out if this is an actual E17 bug or if it's an Arch specific thing??? -- | ~^~ ~^~ | <?> <?> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>>
On 04/16/2010 04:12 PM, Joe(theWordy)Philbrook wrote:
Actually, I'm not sure if this is thanks to E17 itself or specific to Arch... And it's no big deal anyway because: A) e17 is "under heavy development", (And I know that means it's unstable) B) I've already got a workaround that works for me... But I'd like to understand what happened a little better.
<snip>
How can I a regular "Joe user", figure out if this is an actual E17 bug or if it's an Arch specific thing???
Joe, I'll have to check my E17 install on Arch, but I just got through going through fits with E17 on suse. All of a sudden, E17 virtual desktop management and the pager went nuts. If I opened an app on desktop 1 and then switched to desktop 2, etc.. the open app was visible on on desktops. (like you had the window set as sticky to show up on all desktops) Further, E17 would crash every time I tried to change shelf properties or add/remove apps from ibar, etc.. The issues ended up being something in my ~/.e directory. I hadn't changed any settings at all in E17 for quite some time, so one of the E17 updates did something strange to the config that really screwed E17 up. Wiping out my ~/.e directory and restarting with the default black & white theme cured it. After the restart and forced rebuild of the default configuration, I could reconfigure E17 exactly the way I had it before and it worked just fine. If you haven't tried it, it might be worth a shot. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
It would appear that on Apr 17, David C. Rankin did say:
On 04/16/2010 04:12 PM, Joe(theWordy)Philbrook wrote:
<snip>
How can I a regular "Joe user", figure out if this is an actual E17 bug or if it's an Arch specific thing???
Joe,
I'll have to check my E17 install on Arch, but I just got through going through fits with E17 on suse. All of a sudden, E17 virtual desktop management and the pager went nuts. If I opened an app on desktop 1 and then switched to desktop 2, etc.. the open app was visible on on desktops. (like you had the window set as sticky to show up on all desktops)
Further, E17 would crash every time I tried to change shelf properties or add/remove apps from ibar, etc.. The issues ended up being something in my ~/.e directory. I hadn't changed any settings at all in E17 for quite some time, so one of the E17 updates did something strange to the config that really screwed E17 up. Wiping out my ~/.e directory and restarting with the default black & white theme cured it. After the restart and forced rebuild of the default configuration, I could reconfigure E17 exactly the way I had it before and it worked just fine. If you haven't tried it, it might be worth a shot.
Thanks for looking into it David, And for the suggestion. I suppose it could be that something messed with something in my ~/.e file hierarchy That's probably more likely than that something changed in such a way as to make some formerly viable set up to suddenly become incompatible... I really hope that if either is true, it's the former as I really detest rebuilding my keyboard shortcuts with the freaking pointNclick GUI config tool. Especially since there isn't a one that matches the default settings AND my mouse skills are a negative value... {Gawd how I miss the old scriptable pre-dbus enlightenment_remote command. that allowed me to set *_MY_* default keybindings with a bash script as the first thing to do once e17 was installed} At least (if the former is the case) I can use the fact that when I first got it set up the way I liked I did a "cp -R ~/.e ~/tmp/e_bu" (Something I learned to do because with some of my e17 installations the "remember" settings for a few things in my .xintrc kept getting "lost"... {PCLinuxOS comes to mind where I've actually gone so far as to put an "cp -R" in my .bash_profile to restore the original every time I login...}) I'll have to test if restoring the prev version of .e will fix it. After all the only thing I'd lose is the updated keybinding assigning Alt+F2 to xfrun4 instead of the e17 run prompt... Then I suppose (given I can still restore the .e dir if it doesn't help) I could let e17 build me a new default .e ... I'll let you know how it pans out in a day or two. -- | ~^~ ~^~ | <*> <*> Joe (theWordy) Philbrook | ^ J(tWdy)P | \___/ <<jtwdyp@ttlc.net>>
It would appear that on Apr 18, Joe(theWordy)Philbrook did say:
It would appear that on Apr 17, David C. Rankin did say:
On 04/16/2010 04:12 PM, Joe(theWordy)Philbrook wrote:
<snip>
How can I a regular "Joe user", figure out if this is an actual E17 bug or if it's an Arch specific thing???
I'll have to check my E17 install on Arch, but I just got through going through fits with E17 on suse. All of a sudden, E17 virtual desktop management and the pager went nuts. <snip> Wiping out my ~/.e directory and restarting with the default black & white theme cured it. After the restart and forced rebuild of the default configuration, I could reconfigure E17 exactly the way I had it before and it worked just fine. If you haven't tried it, it might be worth a shot.
<snip>
I'll have to test if restoring the prev version of .e will fix it. After all the only thing I'd lose is the updated keybinding assigning Alt+F2 to xfrun4 instead of the e17 run prompt... Then I suppose (given I can still restore the .e dir if it doesn't help) I could let e17 build me a new default .e ... I'll let you know how it pans out in a day or two.
Nah, neither restoring the old .e nor wiping it out and starting with a default worked. Good thing I've got a work around. The enlightenment users list says this currently works properly and suggests I use svn... <sigh> Well at least I've got a work around. (xfrun4 isn't a bad tool...) -- | --- ___ | <0> <-> Joe (theWordy) Philbrook | ^ J(tWdy)P | ~\___/~ <<jtwdyp@ttlc.net>>
participants (2)
-
David C. Rankin
-
Joe(theWordy)Philbrook