Void Linux discussion
 help / color / mirror / Atom feed
From: Userx Xbw <use...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Subject: Enelightenment .29.5_4 causes seg faults
Date: Thu, 23 Jul 2015 14:19:27 -0700 (PDT)	[thread overview]
Message-ID: <db59b29e-1d97-4139-bf36-e624f5e4ad50@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 609 bytes --]

I installed the update to Enelightenment to from 19.5_3 to 19.5_4 and 
started getting segmiation faults just setting there watching a video -- 
more than once to the point of I just said screw this, becuse one cannot 
reenstall an old version that i know of I just dummped the whole system and 
reenisted it then put Enelightenment on hold for updating.


how can it be said it is stable to upgrade everyday and to put trust into 
this system for the upgrades / dates to be stable. when it causes 
segmentation faults after installing them?

makes me leary in ever updating anything especailly E19.5 .... 



[-- Attachment #1.2: Type: text/html, Size: 661 bytes --]

             reply	other threads:[~2015-07-23 21:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 21:19 Userx Xbw [this message]
2015-07-24  7:04 ` Stefan Mühlinghaus
2015-07-24 13:11   ` Christian Neukirchen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=db59b29e-1d97-4139-bf36-e624f5e4ad50@googlegroups.com \
    --to="use..."@gmail.com \
    --cc="void..."@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).