Linux MintThis forum is for the discussion of Linux Mint.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi ilsen. After booting the .iso, before clicking on install (assuming you have internet connectivity) could you open a terminal (or Ctrl+Alt+F2) in this 'live' Mint and post the link from:
lsblk | nc termbin.com 9999 (5.39.93.71 in case dns isn't working)
The idea is: for 'us' to see info about disk space. (there may be better cmds/switches than just lsblk)
I see you filed a bug: great!
(IF you feel like digging, try googling: mint "Installer Crashed")
Interesting FYI: here's SAME as in your .png in post#1 from last year!
A wild-guess: it's possible that the installer has a bug where it breaks with all those partitions.
Theoretically, one could setup a VBox .vdi with exact same partitions! And debug the .py script(s) Paging @justmy2cents
You did not tell me.
I found it now
I understand
"LMDE 2"
I'm downloading right now
but
How can I resolve this error? "Installer Crashed"
But i would like to install linux mint 18.2 cinnamon 64 bit.
You will have the source for the kernel and drivers, you can add debug to the kernel or drivers to aid you with analyzing this. My prior experience with getting Linux to boot, when it doesn't boot, would be to cut away many of the non-necessary items to be able to get it to boot to some degree and then debug the problem using the printk() utility or KDB. Meanwhile, the kernel is booted, however you are trying to run their installer. As pointed out by Jjanel, you can try CTRL-ALT-F2 to open a system console and see what process are running, see if the install process is running, if it is stuck in a wait state, or running, and then try to kill it and see if this returns things to normal. And you can see if the installer is within the code for their kernel, or if you can get the installer source and try to debug it this way.
Have you tried to open a system console? If so, what did you find?
You will have the source for the kernel and drivers, you can add debug to the kernel or drivers to aid you with analyzing this. My prior experience with getting Linux to boot, when it doesn't boot, would be to cut away many of the non-necessary items to be able to get it to boot to some degree and then debug the problem using the printk() utility or KDB. Meanwhile, the kernel is booted, however you are trying to run their installer. As pointed out by Jjanel, you can try CTRL-ALT-F2 to open a system console and see what process are running, see if the install process is running, if it is stuck in a wait state, or running, and then try to kill it and see if this returns things to normal. And you can see if the installer is within the code for their kernel, or if you can get the installer source and try to debug it this way.
Have you tried to open a system console? If so, what did you find?
LMDE-2-201701-mate-64bit
Loading window disappeared while trying to install.
While I realize this is not what you want, give that a try and if it works, then the problem may be the different language and country settings you wish to set.
Those possibly can be changed post installation.
One or the other may be the problem, but it is unknown at this time. Debug by finding out if the language and region settings are the problem for starters.
While I realize this is not what you want, give that a try and if it works, then the problem may be the different language and country settings you wish to set.
Those possibly can be changed post installation.
One or the other may be the problem, but it is unknown at this time. Debug by finding out if the language and region settings are the problem for starters.
While I realize this is not what you want, give that a try and if it works, then the problem may be the different language and country settings you wish to set.
Those possibly can be changed post installation.
One or the other may be the problem, but it is unknown at this time. Debug by finding out if the language and region settings are the problem for starters.
I tried the US and English language setting.
The window is still disappearing.
Why did ubi-prepare.py free_space get IndexError, parsing output of parted_devices cmd?
Code:
...
File "/usr/lib/ubiquity/plugins/ubi-prepare.py", line 410, in free_space
if device and int(device.split('\t')[1]) > biggest:
IndexError: list index out of range
Looking at the error, and line 406 in /usr/lib/ubiquity/plugins/ubi-prepare.py (similar code),
it might be worth checking the output of: [sudo] parted_devices
@rtmistler: thanks for #70->#32, but (I finally discovered) it's M$Win diskmgmt.msc
Maybe try gparted (ideally from the live mint usb, or if not, the installed Ubu/Kali)
This might be useful: [sudo] parted -lm | nc termbin.com 9999
(post link, or output in CODE tags here; maybe add to bug report)
I read parted but got lost on gpt fs/flags vs fdisk types; Idk .py
Code:
def free_space(self):
biggest = 0
with misc.raised_privileges():
proc = subprocess.Popen(
['parted_devices'],
stdout=subprocess.PIPE, universal_newlines=True)
devices = proc.communicate()[0].rstrip('\n').split('\n')
for device in devices:
if device and int(device.split('\t')[1]) > biggest:
biggest = int(device.split('\t')[1])
return biggest
This is something I said earlier. My assessment is that you have tried very many things and proven that there is no normal case causing this problem. Therefore it seems to be a case where you either need to diagnose more directly within their software, or let the issue lie.
Even though this information is more related to getting their kernel to boot, the same efforts would be involved with diagnosing their install utility. It is either a compiled binary or a script. If it is a script, you should be able to start debugging it with what you have. If it is a program, then you should download all their sources and find the source for that install program, and debug that.
You will have the source for the kernel and drivers, you can add debug to the kernel or drivers to aid you with analyzing this. My prior experience with getting Linux to boot, when it doesn't boot, would be to cut away many of the non-necessary items to be able to get it to boot to some degree and then debug the problem using the printk() utility or KDB. Meanwhile, the kernel is booted, however you are trying to run their installer. As pointed out by Jjanel, you can try CTRL-ALT-F2 to open a system console and see what process are running, see if the install process is running, if it is stuck in a wait state, or running, and then try to kill it and see if this returns things to normal. And you can see if the installer is within the code for their kernel, or if you can get the installer source and try to debug it this way.
This is something I said earlier. My assessment is that you have tried very many things and proven that there is no normal case causing this problem. Therefore it seems to be a case where you either need to diagnose more directly within their software, or let the issue lie.
Even though this information is more related to getting their kernel to boot, the same efforts would be involved with diagnosing their install utility. It is either a compiled binary or a script. If it is a script, you should be able to start debugging it with what you have. If it is a program, then you should download all their sources and find the source for that install program, and debug that.
How can i resolve this error?
Does the subject here solve the problem? =================== >>> How to: Compile the latest kernels (Classic Mint & LMDE)
EDIT/update: There might be a way to CLI-install Mint, withOUT GUI! (IhateGUI)
Actually, withOUT darn-buggy UBiqUity! Anyone have any ideas? (Slackware?but no)
Quote:
Originally Posted by ilsen
[1]How can i resolve this error?
[2]Does the subject here solve the problem? =================== >>> How to: Compile the latest kernels (Classic Mint & LMDE)
1: Post the output of this, in CODE tags, or use |nc termbin.com 9999
Code:
parted_devices; parted -lm
"My car makes a noise. How do I fix it, withOUT telling you what I have?"
2: Idk. (rtmistler has wonderfully&generously helped me learn toward writing decently)
My point 1: and prior brief post might help someone provide you resolution.
Best wishes; thanks for your patience on this bug.
EDIT/update: There might be a way to CLI-install Mint, withOUT GUI! (IhateGUI)
Actually, withOUT darn-buggy UBiqUity! Anyone have any ideas? (Slackware?but no)
1: Post the output of this, in CODE tags, or use |nc termbin.com 9999
Code:
parted_devices; parted -lm
"My car makes a noise. How do I fix it, withOUT telling you what I have?"
2: Idk. (rtmistler has wonderfully&generously helped me learn toward writing decently)
My point 1: and prior brief post might help someone provide you resolution.
Best wishes; thanks for your patience on this bug.
"Installer Crashed"
How can I solve this problem?
what is the solution?
This is something I said earlier. My assessment is that you have tried very many things and proven that there is no normal case causing this problem. Therefore it seems to be a case where you either need to diagnose more directly within their software, or let the issue lie.
Even though this information is more related to getting their kernel to boot, the same efforts would be involved with diagnosing their install utility. It is either a compiled binary or a script. If it is a script, you should be able to start debugging it with what you have. If it is a program, then you should download all their sources and find the source for that install program, and debug that.
How can i resolve this error?
Does the subject here solve the problem? =================== >>> How to: Compile the latest kernels (Classic Mint & LMDE)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Paging @justmy2cents 
: There might be a way to 
but no)
