Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #105250 > unrolled thread

crash while using PyCharm / Python3

Back to article view | Back to comp.lang.python

Contents

  crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-18 21:34 -0700
    Re: crash while using PyCharm / Python3 wxjmfauth@gmail.com - 2016-03-19 02:30 -0700
    Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 09:51 -0700
      Re: crash while using PyCharm / Python3 "Dirk T. Verbeek" <dverbeek@xs4all.nl> - 2016-03-21 18:33 +0100
        Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 11:05 -0700
        Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 11:36 -0700
          Re: crash while using PyCharm / Python3 "Jonathan N. Little" <lws4art@gmail.com> - 2016-03-21 15:58 -0400
            Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 15:15 -0700
              Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 17:23 -0700
                Re: crash while using PyCharm / Python3 "Jonathan N. Little" <lws4art@gmail.com> - 2016-03-21 22:58 -0400
                  Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-22 00:41 -0700
                    Re: crash while using PyCharm / Python3 "Jonathan N. Little" <lws4art@gmail.com> - 2016-03-22 09:10 -0400
                      Re: crash while using PyCharm / Python3 Daniel Wilcox <dmw@yubasolutions.com> - 2016-03-22 09:32 -0700
                      Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-22 14:52 -0700
                Re: crash while using PyCharm / Python3 Big Bad Bob <BigBadBob-at-mrp3-dot-com@testing.local> - 2016-03-22 09:39 -0700
                  Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-22 14:52 -0700
          Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 17:36 -0700
            Re: crash while using PyCharm / Python3 "Jonathan N. Little" <lws4art@gmail.com> - 2016-03-21 23:13 -0400
              Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-22 00:46 -0700
      Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-21 10:52 -0700
    Re: crash while using PyCharm / Python3 "Adam" <adam@no_thanks.com> - 2016-03-23 21:18 -0700
      Re: crash while using PyCharm / Python3 Daniel Wilcox <dmw@yubasolutions.com> - 2016-04-02 17:05 -0700

Page 1 of 2  [1] 2  Next page →

#105250 — crash while using PyCharm / Python3

Host OS:    Ubuntu Desktop 14.04 LTS / Unity

System crashed while using PyCharm / Python3.
Booting takes forever and stuck at the purple screen with
the Ubuntu logo and the five dots cycling.
How to fix?

[toc] | [next] | [standalone]

#105258

Le samedi 19 mars 2016 05:34:50 UTC+1, Adam a écrit :
> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
> 
> System crashed while using PyCharm / Python3.
> Booting takes forever and stuck at the purple screen with
> the Ubuntu logo and the five dots cycling.
> How to fix?

I was afraid, you wanted to point the latest
PyCharm has problems with the coding of characters.

(Like LibreOffice and its scripting language).

[toc] | [prev] | [next] | [standalone]

#105372

"Adam" <adam@no_thanks.com> wrote in message 
news:ncikss$tks$1@news.albasani.net...
>
> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
>
> System crashed while using PyCharm / Python3.
> Booting takes forever and stuck at the purple screen with
> the Ubuntu logo and the five dots cycling.
> How to fix?
>

So, I tried Ubuntu repair methods suggested here...

How to Fix an Ubuntu System When It Won't Boot
http://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/
GRUB Boot Loader is accessible but using the recovery mode did not help.
It hangs with "Loading extension GLX" but I forget which command I used.

Then, I tried to...

Reinstall Ubuntu While Keeping Files and Programs

but, I am instead given the following options...
===========================================================
This computer currently has Ubuntu 14.04.4 LTS on it.  What would you like 
to do?

- Erase Ubuntu 14.04.4 LTS and reinstall
    Warning: This will delete all your Ubuntu 14.04.4 LTS programs, 
documents, photos...
- Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS
    Documents, music, and other personal files will be kept.  You can choose 
which operating system...
- Erase disk and install Ubuntu
- Something else
===========================================================

Perhaps, "Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS" is the 
safest ? 

[toc] | [prev] | [next] | [standalone]

#105379

Op 21-03-16 om 17:51 schreef Adam:
> "Adam" <adam@no_thanks.com> wrote in message
> news:ncikss$tks$1@news.albasani.net...
>>
>> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
>>
>> System crashed while using PyCharm / Python3.
>> Booting takes forever and stuck at the purple screen with
>> the Ubuntu logo and the five dots cycling.
>> How to fix?
>>
>
> So, I tried Ubuntu repair methods suggested here...
>
> How to Fix an Ubuntu System When It Won't Boot
> http://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/
> GRUB Boot Loader is accessible but using the recovery mode did not help.
> It hangs with "Loading extension GLX" but I forget which command I used.
>
> Then, I tried to...
>
> Reinstall Ubuntu While Keeping Files and Programs
>
> but, I am instead given the following options...
> ===========================================================
> This computer currently has Ubuntu 14.04.4 LTS on it.  What would you like
> to do?
>
> - Erase Ubuntu 14.04.4 LTS and reinstall
>      Warning: This will delete all your Ubuntu 14.04.4 LTS programs,
> documents, photos...
> - Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS
>      Documents, music, and other personal files will be kept.  You can choose
> which operating system...
> - Erase disk and install Ubuntu
> - Something else
> ===========================================================
>
> Perhaps, "Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS" is the
> safest ?
>
>
It's easy to do a reinstall without wiping documents and application 
configurations/settings PROVIDING you have a separate / (root) and /home 
partition.

During partition you select Manual partitioning and assign the existing 
partitions being VERY careful to NOT format the existing /home.

But / where the OS and all applications reside will need to be 
formatted/deleted/overwritten.

Keeping the configuration on your /home might cause the old error to be 
included in the new install...

Although, you error seems to be the system, not the applications.

[toc] | [prev] | [next] | [standalone]

#105387

"Dirk T. Verbeek" <dverbeek@xs4all.nl> wrote in message 
news:56f03080$0$5924$e4fe514c@news.xs4all.nl...
> Op 21-03-16 om 17:51 schreef Adam:
>> "Adam" <adam@no_thanks.com> wrote in message
>> news:ncikss$tks$1@news.albasani.net...
>>>
>>> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
>>>
>>> System crashed while using PyCharm / Python3.
>>> Booting takes forever and stuck at the purple screen with
>>> the Ubuntu logo and the five dots cycling.
>>> How to fix?
>>>
>>
>> So, I tried Ubuntu repair methods suggested here...
>>
>> How to Fix an Ubuntu System When It Won't Boot
>> http://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/
>> GRUB Boot Loader is accessible but using the recovery mode did not help.
>> It hangs with "Loading extension GLX" but I forget which command I used.
>>
>> Then, I tried to...
>>
>> Reinstall Ubuntu While Keeping Files and Programs
>>
>> but, I am instead given the following options...
>> ===========================================================
>> This computer currently has Ubuntu 14.04.4 LTS on it.  What would you 
>> like
>> to do?
>>
>> - Erase Ubuntu 14.04.4 LTS and reinstall
>>      Warning: This will delete all your Ubuntu 14.04.4 LTS programs,
>> documents, photos...
>> - Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS
>>      Documents, music, and other personal files will be kept.  You can 
>> choose
>> which operating system...
>> - Erase disk and install Ubuntu
>> - Something else
>> ===========================================================
>>
>> Perhaps, "Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS" is the
>> safest ?
>>
>>
> It's easy to do a reinstall without wiping documents and application 
> configurations/settings PROVIDING you have a separate / (root) and /home 
> partition.

Yes, I have a separate /home partition.


>
> During partition you select Manual partitioning and assign the existing 
> partitions being VERY careful to NOT format the existing /home.
>
> But / where the OS and all applications reside will need to be 
> formatted/deleted/overwritten.
>
> Keeping the configuration on your /home might cause the old error to be 
> included in the new install...
>
> Although, you error seems to be the system, not the applications.

I think it's a system issue as well.  The problem happened almost right 
after
creating a python3 virtual environment using PyCharm.
There were two checkboxes (both "Inherit global site-packages" and
"Make available to all projects" were checked).
Can this be the problem ? 

[toc] | [prev] | [next] | [standalone]

#105391

"Dirk T. Verbeek" <dverbeek@xs4all.nl> wrote in message 
news:56f03080$0$5924$e4fe514c@news.xs4all.nl...
> Op 21-03-16 om 17:51 schreef Adam:
>> "Adam" <adam@no_thanks.com> wrote in message
>> news:ncikss$tks$1@news.albasani.net...
>>>
>>> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
>>>
>>> System crashed while using PyCharm / Python3.
>>> Booting takes forever and stuck at the purple screen with
>>> the Ubuntu logo and the five dots cycling.
>>> How to fix?
>>>
>>
>> So, I tried Ubuntu repair methods suggested here...
>>
>> How to Fix an Ubuntu System When It Won't Boot
>> http://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/
>> GRUB Boot Loader is accessible but using the recovery mode did not help.
>> It hangs with "Loading extension GLX" but I forget which command I used.
>>
>> Then, I tried to...
>>
>> Reinstall Ubuntu While Keeping Files and Programs
>>
>> but, I am instead given the following options...
>> ===========================================================
>> This computer currently has Ubuntu 14.04.4 LTS on it.  What would you 
>> like
>> to do?
>>
>> - Erase Ubuntu 14.04.4 LTS and reinstall
>>      Warning: This will delete all your Ubuntu 14.04.4 LTS programs,
>> documents, photos...
>> - Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS
>>      Documents, music, and other personal files will be kept.  You can 
>> choose
>> which operating system...
>> - Erase disk and install Ubuntu
>> - Something else
>> ===========================================================
>>
>> Perhaps, "Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS" is the
>> safest ?
>>
>>
> It's easy to do a reinstall without wiping documents and application 
> configurations/settings PROVIDING you have a separate / (root) and /home 
> partition.
>
> During partition you select Manual partitioning and assign the existing 
> partitions being VERY careful to NOT format the existing /home.
>
> But / where the OS and all applications reside will need to be 
> formatted/deleted/overwritten.

I guess I can do something like...

$ dpkg --get-selections \*    |    awk '{print $1}'    >    ~/package_list
$ cat ~/package_list    |    sudo xargs -l1 aptitude reinstall

to reinstall packages that were installed after installing Ubuntu.

There ought to be a way to just reinstall the graphics subsystem rather than
an all-or-none installation approach.


>
> Keeping the configuration on your /home might cause the old error to be 
> included in the new install...
>
> Although, you error seems to be the system, not the applications. 

[toc] | [prev] | [next] | [standalone]

#105399

Adam wrote:
> There ought to be a way to just reinstall the graphics subsystem rather than
> an all-or-none installation approach.

Yes you can. Did it for a borked install of the nVidia driver. reference 
this:

<https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#105411

"Jonathan N. Little" <lws4art@gmail.com> wrote in message 
news:ncpjj0$7ug$1@dont-email.me...
> Adam wrote:
>> There ought to be a way to just reinstall the graphics subsystem rather 
>> than
>> an all-or-none installation approach.
>
> Yes you can. Did it for a borked install of the nVidia driver. reference 
> this:
>
> <https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>

Thanks, even after doing the following...
Problem: Need to purge -fglrx
Typically, the following manual commands will properly uninstall -fglrx:


  sudo apt-get remove --purge xorg-driver-fglrx fglrx*
  sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri 
xserver-xorg-core
  sudo dpkg-reconfigure xserver-xorgI still get that dreaded "The system is 
running in low-graphics mode" error.
And, recovery mode failsafeX and Ctrl+Alt+F1 hangs with the following...

    <more of the same>
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
<hangs here>


>
> -- 
> Take care,
>
> Jonathan
> -------------------
> LITTLE WORKS STUDIO
> http://www.LittleWorksStudio.com 

[toc] | [prev] | [next] | [standalone]

#105424

"Adam" <adam@no_thanks.com> wrote in message 
news:ncprqb$tl9$1@news.albasani.net...
>
> "Jonathan N. Little" <lws4art@gmail.com> wrote in message 
> news:ncpjj0$7ug$1@dont-email.me...
>> Adam wrote:
>>> There ought to be a way to just reinstall the graphics subsystem rather 
>>> than
>>> an all-or-none installation approach.
>>
>> Yes you can. Did it for a borked install of the nVidia driver. reference 
>> this:
>>
>> <https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>
>
> Thanks, even after doing the following...
>
> Problem: Need to purge -fglrx
>
> Typically, the following manual commands will properly uninstall -fglrx:
>
>  $ sudo apt-get remove --purge xorg-driver-fglrx fglrx*
>  $ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri 
> xserver-xorg-core
>  $ sudo dpkg-reconfigure xserver-xorg
>
> I still get that dreaded "The system is running in low-graphics mode" 
> error.
> And, recovery mode failsafeX and Ctrl+Alt+F1 hangs with the following...
>
>    <more of the same>
> Initializing built-in extension MIT-SCREEN-SAVER
> Initializing built-in extension DOUBLE-BUFFER
> Initializing built-in extension RECORD
> Initializing built-in extension DPMS
> Initializing built-in extension Present
> Initializing built-in extension DRI3
> Initializing built-in extension X-Resource
> Initializing built-in extension XVideo
> Initializing built-in extension XVideo-MotionCompensation
> Initializing built-in extension SELinux
> Initializing built-in extension XFree86-VidModeExtension
> Initializing built-in extension XFree86-DGA
> Initializing built-in extension XFree86-DRI
> Initializing built-in extension DRI2
> Loading extension GLX
> <hangs here>
>

After trying the following...

http://askubuntu.com/questions/577093/how-to-install-gnome-desktop

$ sudo apt-get update
$ sudo apt-get install gnome-shell


http://tipsonubuntu.com/2014/06/06/change-display-manager-ubuntu-14-04/

$ sudo dpkg-reconfigure lightdm

I am now able to login.  But,
not sure what happened to the "lightdm" display manager.
I am now using "gdm" display manager.


>
>>
>> -- 
>> Take care,
>>
>> Jonathan
>> -------------------
>> LITTLE WORKS STUDIO
>> http://www.LittleWorksStudio.com
>
> 

[toc] | [prev] | [next] | [standalone]

#105436

Adam wrote:
> "Adam" <adam@no_thanks.com> wrote in message
> news:ncprqb$tl9$1@news.albasani.net...
>>
>> "Jonathan N. Little" <lws4art@gmail.com> wrote in message
>> news:ncpjj0$7ug$1@dont-email.me...
>>> Adam wrote:
>>>> There ought to be a way to just reinstall the graphics subsystem rather
>>>> than
>>>> an all-or-none installation approach.
>>>
>>> Yes you can. Did it for a borked install of the nVidia driver. reference
>>> this:
>>>
>>> <https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>
>>
>> Thanks, even after doing the following...
>>
>> Problem: Need to purge -fglrx
>>
>> Typically, the following manual commands will properly uninstall -fglrx:
>>
>>   $ sudo apt-get remove --purge xorg-driver-fglrx fglrx*
>>   $ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri
>> xserver-xorg-core
>>   $ sudo dpkg-reconfigure xserver-xorg
>>
>> I still get that dreaded "The system is running in low-graphics mode"
>> error.
>> And, recovery mode failsafeX and Ctrl+Alt+F1 hangs with the following...
>>
>>     <more of the same>
>> Initializing built-in extension MIT-SCREEN-SAVER
>> Initializing built-in extension DOUBLE-BUFFER
>> Initializing built-in extension RECORD
>> Initializing built-in extension DPMS
>> Initializing built-in extension Present
>> Initializing built-in extension DRI3
>> Initializing built-in extension X-Resource
>> Initializing built-in extension XVideo
>> Initializing built-in extension XVideo-MotionCompensation
>> Initializing built-in extension SELinux
>> Initializing built-in extension XFree86-VidModeExtension
>> Initializing built-in extension XFree86-DGA
>> Initializing built-in extension XFree86-DRI
>> Initializing built-in extension DRI2
>> Loading extension GLX
>> <hangs here>
>>
>
> After trying the following...
>
> http://askubuntu.com/questions/577093/how-to-install-gnome-desktop
>
> $ sudo apt-get update
> $ sudo apt-get install gnome-shell
>
>
> http://tipsonubuntu.com/2014/06/06/change-display-manager-ubuntu-14-04/
>
> $ sudo dpkg-reconfigure lightdm

Not sure about ATI, but when you purge the nVidia driver it takes Unity 
with it so I had to reinstall unity-desktop afterwards. If you want 
lightdm but are now using gdm, maybe it happened because unity-desktop 
was uninstalled and you just installed gnome-shell, your can reset:

sudo dpkg-reconfigure gdm

and select lightdm from the list.


-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#105448

"Jonathan N. Little" <lws4art@gmail.com> wrote in message 
news:ncqc7j$na1$1@dont-email.me...
> Adam wrote:
>> "Adam" <adam@no_thanks.com> wrote in message
>> news:ncprqb$tl9$1@news.albasani.net...
>>>
>>> "Jonathan N. Little" <lws4art@gmail.com> wrote in message
>>> news:ncpjj0$7ug$1@dont-email.me...
>>>> Adam wrote:
>>>>> There ought to be a way to just reinstall the graphics subsystem 
>>>>> rather
>>>>> than
>>>>> an all-or-none installation approach.
>>>>
>>>> Yes you can. Did it for a borked install of the nVidia driver. 
>>>> reference
>>>> this:
>>>>
>>>> <https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>
>>>
>>> Thanks, even after doing the following...
>>>
>>> Problem: Need to purge -fglrx
>>>
>>> Typically, the following manual commands will properly uninstall -fglrx:
>>>
>>>   $ sudo apt-get remove --purge xorg-driver-fglrx fglrx*
>>>   $ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri
>>> xserver-xorg-core
>>>   $ sudo dpkg-reconfigure xserver-xorg
>>>
>>> I still get that dreaded "The system is running in low-graphics mode"
>>> error.
>>> And, recovery mode failsafeX and Ctrl+Alt+F1 hangs with the following...
>>>
>>>     <more of the same>
>>> Initializing built-in extension MIT-SCREEN-SAVER
>>> Initializing built-in extension DOUBLE-BUFFER
>>> Initializing built-in extension RECORD
>>> Initializing built-in extension DPMS
>>> Initializing built-in extension Present
>>> Initializing built-in extension DRI3
>>> Initializing built-in extension X-Resource
>>> Initializing built-in extension XVideo
>>> Initializing built-in extension XVideo-MotionCompensation
>>> Initializing built-in extension SELinux
>>> Initializing built-in extension XFree86-VidModeExtension
>>> Initializing built-in extension XFree86-DGA
>>> Initializing built-in extension XFree86-DRI
>>> Initializing built-in extension DRI2
>>> Loading extension GLX
>>> <hangs here>
>>>
>>
>> After trying the following...
>>
>> http://askubuntu.com/questions/577093/how-to-install-gnome-desktop
>>
>> $ sudo apt-get update
>> $ sudo apt-get install gnome-shell
>>
>>
>> http://tipsonubuntu.com/2014/06/06/change-display-manager-ubuntu-14-04/
>>
>> $ sudo dpkg-reconfigure lightdm
>
> Not sure about ATI, but when you purge the nVidia driver it takes Unity 
> with it so I had to reinstall unity-desktop afterwards. If you want 
> lightdm but are now using gdm, maybe it happened because unity-desktop was 
> uninstalled and you just installed gnome-shell, your can reset:
>
> sudo dpkg-reconfigure gdm
>
> and select lightdm from the list.
>

Thanks, but why fix if it ain't broke?    :-)


>
> -- 
> Take care,
>
> Jonathan
> -------------------
> LITTLE WORKS STUDIO
> http://www.LittleWorksStudio.com 

[toc] | [prev] | [next] | [standalone]

#105478

Adam wrote:
> Thanks, but why fix if it ain't broke?:-)

No reason to.

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#105496

Now as for *why* you needed to reinstall your graphics driver... did the
graphics driver get updated before the crash?  Or do we think something in
the java runtime for PyCharm ate libglx or friends?

I did find this PyCharm crash in which Java ate itself -- though didn't eat
any library files (as that is *very* special) -- going on out a limb here
maybe the crash was something like this, sans the markdown plugin:
https://github.com/nicoulaj/idea-markdown/issues/247

<snip>
7f7b38dd9000 r-xp 00000000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7f7b38dd9000-7f7b38fd8000 ---p 00015000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7f7b38fd8000-7f7b38fda000 r--p 00014000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.so.0.0.0
7f7b38fda000-7f7b38fdb000 rw-p 00016000 08:06 926862
/usr/lib/x86_64-linux-gnu/libxcb-glx.s</snip>

So some xcb libraries do get mapped -- but that doesn't say much really --
after all paging a library in shouldn't lead to writing to it, corrupting
it -- but copy-on-write and all that crap... so maybe.

Also from some quick reading on XCD it doesn't sound like it has anything
to do with initializing the graphics system, which is still GLX+Xlib's
job.  So whether this could even affect you at startup isn't clear to me.

https://xcb.freedesktop.org/opengl/

Late to the party but glad to hear everything worked out.  It's been
literally a decade since I worried about having working 3d graphics in
Linux, so nouveau for me.  Cheers!


On Tue, Mar 22, 2016 at 6:10 AM, Jonathan N. Little <lws4art@gmail.com>
wrote:

> Adam wrote:
>
>> Thanks, but why fix if it ain't broke?:-)
>>
>
> No reason to.
>
>
> --
> Take care,
>
> Jonathan
> -------------------
> LITTLE WORKS STUDIO
> http://www.LittleWorksStudio.com
> --
> https://mail.python.org/mailman/listinfo/python-list
>

[toc] | [prev] | [next] | [standalone]

#105502

"Jonathan N. Little" <lws4art@gmail.com> wrote in message 
news:ncrg2v$jo$2@dont-email.me...
> Adam wrote:
>> Thanks, but why fix if it ain't broke?    :-)
>
> No reason to.

Yup, I agree.


>
> -- 
> Take care,
>
> Jonathan
> -------------------
> LITTLE WORKS STUDIO
> http://www.LittleWorksStudio.com 

[toc] | [prev] | [next] | [standalone]

#105497

On 03/21/16 17:23, Adam so wittily quipped:
> "Adam" <adam@no_thanks.com> wrote in message 
> news:ncprqb$tl9$1@news.albasani.net...
>>
>> "Jonathan N. Little" <lws4art@gmail.com> wrote in message 
>> news:ncpjj0$7ug$1@dont-email.me...
>>> Adam wrote:
>>>> There ought to be a way to just reinstall the graphics subsystem rather 
>>>> than
>>>> an all-or-none installation approach.
>>>
>>> Yes you can. Did it for a borked install of the nVidia driver. reference 
>>> this:
>>>
>>> <https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>
>>
>> Thanks, even after doing the following...
>>
>> Problem: Need to purge -fglrx
>>
>> Typically, the following manual commands will properly uninstall -fglrx:
>>
>>  $ sudo apt-get remove --purge xorg-driver-fglrx fglrx*
>>  $ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri 
>> xserver-xorg-core
>>  $ sudo dpkg-reconfigure xserver-xorg
>>
>> I still get that dreaded "The system is running in low-graphics mode" 
>> error.
>> And, recovery mode failsafeX and Ctrl+Alt+F1 hangs with the following...
>>
>>    <more of the same>
>> Initializing built-in extension MIT-SCREEN-SAVER
>> Initializing built-in extension DOUBLE-BUFFER
>> Initializing built-in extension RECORD
>> Initializing built-in extension DPMS
>> Initializing built-in extension Present
>> Initializing built-in extension DRI3
>> Initializing built-in extension X-Resource
>> Initializing built-in extension XVideo
>> Initializing built-in extension XVideo-MotionCompensation
>> Initializing built-in extension SELinux
>> Initializing built-in extension XFree86-VidModeExtension
>> Initializing built-in extension XFree86-DGA
>> Initializing built-in extension XFree86-DRI
>> Initializing built-in extension DRI2
>> Loading extension GLX
>> <hangs here>
>>
> 
> After trying the following...
> 
> http://askubuntu.com/questions/577093/how-to-install-gnome-desktop
> 
> $ sudo apt-get update
> $ sudo apt-get install gnome-shell
> 
> 
> http://tipsonubuntu.com/2014/06/06/change-display-manager-ubuntu-14-04/
> 
> $ sudo dpkg-reconfigure lightdm
> 
> I am now able to login.  But,
> not sure what happened to the "lightdm" display manager.
> I am now using "gdm" display manager.

if you're able to boot up by changing things *like* the display manager,
you might want to take a look at the X11 configuration directly.  Adding
"more cruft" to your system (i.e. gdm) isn't necessarily going to 'fix'
a problem that's related to the X11 configuration.

[it's one reason why I generally prefer to boot to command line rather
than into a GUI for a typical linux install]

as an example, you could save your xorg.conf file
  /etc/X11/xorg.conf

and generate a new one, using 'xorg -configure' (as root).

I'm guessing that when you installed the 'PyCharm' package, "some other
dependent package" did something undesirable to your xorg.conf file.

That would MOST CERTAINLY cause a hang during the desktop startup.

it might also be fixable by re-configuring your installed packages,
rather than a full-blown re-install from scratch.

dpkg-reconfigure -a

[the man page warns "it may take a long time" - yeah, probably will]


Keep in mind that adding gdm afterwards *might* have done the
'reconfigure' on the problem package(s) already.  So adding 'gdm'
instead of whatever login manager you were using before [along with all
of its dependent packages] would most likely have forced "the problem
package" to re-configure.  That very well might have "fixed" the problem
on its own.  So my suggestion here would be to remove this 'new' package
and see if the problem comes back.  Most likely it won't.

[toc] | [prev] | [next] | [standalone]

#105501

"Big Bad Bob" <BigBadBob-at-mrp3-dot-com@testing.local> wrote in message 
news:mp6dnaVAhbnh6GzLnZ2dnUU7-Y_NnZ2d@earthlink.com...
> On 03/21/16 17:23, Adam so wittily quipped:
>> "Adam" <adam@no_thanks.com> wrote in message
>> news:ncprqb$tl9$1@news.albasani.net...
>>>
>>> "Jonathan N. Little" <lws4art@gmail.com> wrote in message
>>> news:ncpjj0$7ug$1@dont-email.me...
>>>> Adam wrote:
>>>>> There ought to be a way to just reinstall the graphics subsystem 
>>>>> rather
>>>>> than
>>>>> an all-or-none installation approach.
>>>>
>>>> Yes you can. Did it for a borked install of the nVidia driver. 
>>>> reference
>>>> this:
>>>>
>>>> <https://wiki.ubuntu.com/X/Troubleshooting/VideoDriverDetection#Problem:_Need_to_purge_-fglrx>
>>>
>>> Thanks, even after doing the following...
>>>
>>> Problem: Need to purge -fglrx
>>>
>>> Typically, the following manual commands will properly uninstall -fglrx:
>>>
>>>  $ sudo apt-get remove --purge xorg-driver-fglrx fglrx*
>>>  $ sudo apt-get install --reinstall libgl1-mesa-glx libgl1-mesa-dri
>>> xserver-xorg-core
>>>  $ sudo dpkg-reconfigure xserver-xorg
>>>
>>> I still get that dreaded "The system is running in low-graphics mode"
>>> error.
>>> And, recovery mode failsafeX and Ctrl+Alt+F1 hangs with the following...
>>>
>>>    <more of the same>
>>> Initializing built-in extension MIT-SCREEN-SAVER
>>> Initializing built-in extension DOUBLE-BUFFER
>>> Initializing built-in extension RECORD
>>> Initializing built-in extension DPMS
>>> Initializing built-in extension Present
>>> Initializing built-in extension DRI3
>>> Initializing built-in extension X-Resource
>>> Initializing built-in extension XVideo
>>> Initializing built-in extension XVideo-MotionCompensation
>>> Initializing built-in extension SELinux
>>> Initializing built-in extension XFree86-VidModeExtension
>>> Initializing built-in extension XFree86-DGA
>>> Initializing built-in extension XFree86-DRI
>>> Initializing built-in extension DRI2
>>> Loading extension GLX
>>> <hangs here>
>>>
>>
>> After trying the following...
>>
>> http://askubuntu.com/questions/577093/how-to-install-gnome-desktop
>>
>> $ sudo apt-get update
>> $ sudo apt-get install gnome-shell
>>
>>
>> http://tipsonubuntu.com/2014/06/06/change-display-manager-ubuntu-14-04/
>>
>> $ sudo dpkg-reconfigure lightdm
>>
>> I am now able to login.  But,
>> not sure what happened to the "lightdm" display manager.
>> I am now using "gdm" display manager.
>
> if you're able to boot up by changing things *like* the display manager,
> you might want to take a look at the X11 configuration directly.  Adding
> "more cruft" to your system (i.e. gdm) isn't necessarily going to 'fix'
> a problem that's related to the X11 configuration.
>
> [it's one reason why I generally prefer to boot to command line rather
> than into a GUI for a typical linux install]
>
> as an example, you could save your xorg.conf file
>  /etc/X11/xorg.conf

No such file on my system.  Is it even needed ?


>
> and generate a new one, using 'xorg -configure' (as root).
>
> I'm guessing that when you installed the 'PyCharm' package, "some other
> dependent package" did something undesirable to your xorg.conf file.

I no longer think PyCharm / Python3 is the cause of the crash.
It was just a coincidence.

Search for "lightdm problem ubuntu 14.04"


>
> That would MOST CERTAINLY cause a hang during the desktop startup.

lightdm was failing.


>
> it might also be fixable by re-configuring your installed packages,
> rather than a full-blown re-install from scratch.
>
> dpkg-reconfigure -a
>
> [the man page warns "it may take a long time" - yeah, probably will]
>
>
> Keep in mind that adding gdm afterwards *might* have done the
> 'reconfigure' on the problem package(s) already.  So adding 'gdm'
> instead of whatever login manager you were using before [along with all
> of its dependent packages] would most likely have forced "the problem
> package" to re-configure.  That very well might have "fixed" the problem
> on its own.  So my suggestion here would be to remove this 'new' package
> and see if the problem comes back.  Most likely it won't.
>

Thanks, but it's working fine now.    :-)

[toc] | [prev] | [next] | [standalone]

#105425

"Adam" <adam@no_thanks.com> wrote in message 
news:ncpev8$51d$1@news.albasani.net...
>
> "Dirk T. Verbeek" <dverbeek@xs4all.nl> wrote in message 
> news:56f03080$0$5924$e4fe514c@news.xs4all.nl...
>> Op 21-03-16 om 17:51 schreef Adam:
>>> "Adam" <adam@no_thanks.com> wrote in message
>>> news:ncikss$tks$1@news.albasani.net...
>>>>
>>>> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
>>>>
>>>> System crashed while using PyCharm / Python3.
>>>> Booting takes forever and stuck at the purple screen with
>>>> the Ubuntu logo and the five dots cycling.
>>>> How to fix?
>>>>
>>>
>>> So, I tried Ubuntu repair methods suggested here...
>>>
>>> How to Fix an Ubuntu System When It Won't Boot
>>> http://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/
>>> GRUB Boot Loader is accessible but using the recovery mode did not help.
>>> It hangs with "Loading extension GLX" but I forget which command I used.
>>>
>>> Then, I tried to...
>>>
>>> Reinstall Ubuntu While Keeping Files and Programs
>>>
>>> but, I am instead given the following options...
>>> ===========================================================
>>> This computer currently has Ubuntu 14.04.4 LTS on it.  What would you 
>>> like
>>> to do?
>>>
>>> - Erase Ubuntu 14.04.4 LTS and reinstall
>>>      Warning: This will delete all your Ubuntu 14.04.4 LTS programs,
>>> documents, photos...
>>> - Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS
>>>      Documents, music, and other personal files will be kept.  You can 
>>> choose
>>> which operating system...
>>> - Erase disk and install Ubuntu
>>> - Something else
>>> ===========================================================
>>>
>>> Perhaps, "Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS" is 
>>> the
>>> safest ?
>>>
>>>
>> It's easy to do a reinstall without wiping documents and application 
>> configurations/settings PROVIDING you have a separate / (root) and /home 
>> partition.
>>
>> During partition you select Manual partitioning and assign the existing 
>> partitions being VERY careful to NOT format the existing /home.
>>
>> But / where the OS and all applications reside will need to be 
>> formatted/deleted/overwritten.
>
> I guess I can do something like...
>
> $ dpkg --get-selections \*    |    awk '{print $1}'    >    ~/package_list
> $ cat ~/package_list    |    sudo xargs -l1 aptitude reinstall
>
> to reinstall packages that were installed after installing Ubuntu.
>
> There ought to be a way to just reinstall the graphics subsystem rather 
> than
> an all-or-none installation approach.
>

Sure glad I did not reinstall Ubuntu.  Whew!!


>
>>
>> Keeping the configuration on your /home might cause the old error to be 
>> included in the new install...
>>
>> Although, you error seems to be the system, not the applications.
>
> 

[toc] | [prev] | [next] | [standalone]

#105437

Adam wrote:
> Sure glad I did not reinstall Ubuntu.  Whew!!

Unless you really-really-really screw things up, you usually do not have 
to. Linux is not Windows ;-) Even if you had to, with /home on its own 
partition a reinstall would not have been an issue, you just have to 
choose the "Something Else" on partitioning and only format the "/" and 
set the "/home" partition mount point and NOT FORMAT it.

A tip: If you use gparted or e2label and give partitions labels. Makes 
moving partitions and data easier...

sda1 "12.04-root"
sda5 "old-home"

sdb1 "14.04-root"
sdb5 "new-home"

So from a live session when I mount both drives it is easy to keep 
things straight when I copy my profiles from old drive on sda to new 
drive with newer version of Ubuntu on sdb...

-- 
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

[toc] | [prev] | [next] | [standalone]

#105450

"Jonathan N. Little" <lws4art@gmail.com> wrote in message 
news:ncqd2d$pab$1@dont-email.me...
> Adam wrote:
>> Sure glad I did not reinstall Ubuntu.  Whew!!
>
> Unless you really-really-really screw things up, you usually do not have 
> to. Linux is not Windows ;-) Even if you had to, with /home on its own 
> partition a reinstall would not have been an issue, you just have to 
> choose the "Something Else" on partitioning and only format the "/" and 
> set the "/home" partition mount point and NOT FORMAT it.

I would have to install additional apps all over again.  Ick!!


>
> A tip: If you use gparted or e2label and give partitions labels. Makes 
> moving partitions and data easier...
>
> sda1 "12.04-root"
> sda5 "old-home"
>
> sdb1 "14.04-root"
> sdb5 "new-home"

Thanks, I'll keep this in mind.


>
> So from a live session when I mount both drives it is easy to keep things 
> straight when I copy my profiles from old drive on sda to new drive with 
> newer version of Ubuntu on sdb...
>
> -- 
> Take care,
>
> Jonathan
> -------------------
> LITTLE WORKS STUDIO
> http://www.LittleWorksStudio.com 

[toc] | [prev] | [next] | [standalone]

#105384

"Adam" <adam@no_thanks.com> wrote in message 
news:ncp8r1$ofd$1@news.albasani.net...
>
> "Adam" <adam@no_thanks.com> wrote in message 
> news:ncikss$tks$1@news.albasani.net...
>>
>> Host OS:    Ubuntu Desktop 14.04 LTS / Unity
>>
>> System crashed while using PyCharm / Python3.
>> Booting takes forever and stuck at the purple screen with
>> the Ubuntu logo and the five dots cycling.
>> How to fix?
>>
>
> So, I tried Ubuntu repair methods suggested here...
>
> How to Fix an Ubuntu System When It Won't Boot
> http://www.howtogeek.com/196740/how-to-fix-an-ubuntu-system-when-it-wont-boot/
> GRUB Boot Loader is accessible but using the recovery mode did not help.
> It hangs with "Loading extension GLX" but I forget which command I used.

I remember now, failsafeX and Ctrl+Alt+F1 from here...
http://askubuntu.com/questions/141606/how-to-fix-the-system-is-running-in-low-graphics-mode-error

But, still getting "The system is running in low-graphics mode" error.  How 
to fix?
The problem does not appear to be due to low disk space.
At least, it's no longer stuck at the purple screen with
the Ubuntu logo and the five dots cycling.
So, I will hold off reinstalling Ubuntu for now.


>
> Then, I tried to...
>
> Reinstall Ubuntu While Keeping Files and Programs
>
> but, I am instead given the following options...
> ===========================================================
> This computer currently has Ubuntu 14.04.4 LTS on it.  What would you like 
> to do?
>
> - Erase Ubuntu 14.04.4 LTS and reinstall
>    Warning: This will delete all your Ubuntu 14.04.4 LTS programs, 
> documents, photos...
> - Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS
>    Documents, music, and other personal files will be kept.  You can 
> choose which operating system...
> - Erase disk and install Ubuntu
> - Something else
> ===========================================================
>
> Perhaps, "Install Ubuntu 14.04.4 LTS alongside Ubuntu 14.04.4 LTS" is the 
> safest ?
> 

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.lang.python

csiph-web