Siduction Forum

Siduction Forum => Installation - Support => Topic started by: marky on 2017/03/06, 11:58:39

Title: Calamares fails big time for me.
Post by: marky on 2017/03/06, 11:58:39
Recently I've tried to install Manjaro, same thing.
No matter what, Calamares installation window shows for a split of a second and disappears.

Any thoughts, please?

Code: [Select]
siducer@siduction:~$ sudo calamares install -d
11:49:09 [1]: Calamares version: 3.1.0
Translation: Calamares: Using system locale: "pl_PL"
Translation: Qt: Using default locale, system locale one not found: "pl_PL"
11:49:09 [1]: Default font =====
Pixel size:    -1
Point size:    9
Point sizeF:   9
Font family:   "Sans Serif"
Metric height: 14
11:49:09 [1]: Font height: 14
11:49:09 [1]: Available languages: ("ar", "ast", "bg", "ca", "cs_CZ", "da", "de", "el", "en", "en_GB", "es_MX", "es", "eu", "fr", "hr", "hu", "id", "is", "it_IT", "ja", "lt", "nl", "pl", "pt_BR", "pt_PT", "ro", "ru", "sk", "sv", "th", "tr_TR", "zh_CN", "zh_TW")
11:49:09 [1]: CalamaresApplication thread: 0x5594c33161b0
11:49:09 [1]: Using log file: "/root/.cache/Calamares/Calamares/Calamares.log"
11:49:09 [1]: Using Calamares settings file at "/etc/calamares/settings.conf"
11:49:09 [1]: Using Calamares branding file at "/etc/calamares/branding/siduction/branding.desc"
11:49:09 [1]: WARNING: the selected branding component does not ship translations.
11:49:09 [1]: Loaded branding component "siduction"
11:49:09 [1]: STARTUP: initQmlPath, initSettings, initBranding done
11:49:09 [1]: STARTUP: initModuleManager: module init started
11:49:09 [1]: STARTUP: initModuleManager: all modules init done
11:49:09 [1]: STARTUP: initJobQueue done
11:49:09 [1]: Proposed window size: 1010 520
11:49:09 [1]: STARTUP: CalamaresWindow created; loadModules started
11:49:09 [1]: Initial locale  "pl_PL"
11:49:09 [8]: Translation: Calamares: Using system locale: "pl_PL"
11:49:09 [8]: Translation: Qt: Using default locale, system locale one not found: "pl_PL"
11:49:09 [1]: ViewModule "welcome@welcome" loading complete.
11:49:09 [0]: Qt WebEngine seems to be initialized from a plugin. Please set Qt::AA_ShareOpenGLContexts using QCoreApplication::setAttribute before constructing QGuiApplication.
11:49:09 [1]: ViewModule "webview@webview" loading complete.
11:49:09 [1]: WARNING: cannot acquire a list of available locales. The locale and localecfg modules will be broken as long as this system does not provide  * a /usr/share/i18n/SUPPORTED file     OR  * a well-formed /etc/locale.gen     OR  * a complete pre-compiled locale-gen database which allows complete locale -a output.
11:49:09 [1]: ViewModule "locale@locale" loading complete.
11:49:10 [1]: ViewModule "keyboard@keyboard" loading complete.
11:49:10 [8]: Loaded backend plugin:  "pmlibpartedbackendplugin"
11:49:10 [1]: ViewModule "partition@partition" loading complete.
11:49:10 [1]: ViewModule "users@users" loading complete.
11:49:10 [1]: ViewModule "summary@summary" loading complete.
11:49:10 [1]: Module "partition@partition" already loaded.
11:49:10 [1]: QML import paths: ("/usr/share/calamares/qml", "/usr/bin", "qrc:/qt-project.org/imports", "/usr/lib/x86_64-linux-gnu/qt5/qml")
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: Module "locale@locale" already loaded.
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: Module "keyboard@keyboard" already loaded.
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: Module "users@users" already loaded.
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [0]: void Calamares::Module::loadConfigurationFile(const QString&) bad module configuration format "/usr/share/calamares/modules/umount.conf"
11:49:10 [1]: LAST VS IS EVS!
11:49:10 [1]: ViewModule "finished@finished" loading complete.
11:49:10 [1]: STARTUP: loadModules for all modules done
11:49:10 [1]: STARTUP: Window now visible and ProgressTreeView populated
11:49:10 [1]: WARNING: cannot acquire a list of available locales. The locale and localecfg modules will be broken as long as this system does not provide  * a /usr/share/i18n/SUPPORTED file     OR  * a well-formed /etc/locale.gen     OR  * a complete pre-compiled locale-gen database which allows complete locale -a output.
11:49:10 [1]: Need at least storage bytes: 5905580032
11:49:10 [8]: getting temp failed for  "/dev/sda" :  Nie ma takiego pliku ani katalogu
11:49:10 [8]: getting smart status failed for  "/dev/sdc" :  Operacja nie obsługiwana
11:49:13 [8]: getting smart status failed for  "/dev/sdd" :  Operacja nie obsługiwana
11:49:13 [1]: Need at least ram bytes: 1073741824
11:49:13 [1]: enoughStorage, enoughRam, hasPower, hasInternet, isRoot:  true true true true true
No layout variant specified on the command line
Trailing -variant option ignored
11:49:13 [1]: xkbmap selection changed to:  "pl" - ""
Backtrace has 18 calls on stack:
  18: /lib/x86_64-linux-gnu/libparted.so.2(ped_assert+0x45) [0x7fab02ffbfc5]
  17: /lib/x86_64-linux-gnu/libparted.so.2(ped_device_read+0x78) [0x7fab02ffc758]
  16: /lib/x86_64-linux-gnu/libparted.so.2(ped_geometry_read+0x35) [0x7fab03002555]
  15: /lib/x86_64-linux-gnu/libparted.so.2(nilfs2_probe+0xcb) [0x7fab0300ba2b]
  14: /lib/x86_64-linux-gnu/libparted.so.2(ped_file_system_probe_specific+0x36) [0x7fab02ffd3d6]
  13: /lib/x86_64-linux-gnu/libparted.so.2(ped_file_system_probe+0x61) [0x7fab02ffd4b1]
  12: /lib/x86_64-linux-gnu/libparted.so.2(+0x233b4) [0x7fab030123b4]
  11: /lib/x86_64-linux-gnu/libparted.so.2(+0x24455) [0x7fab03013455]
  10: /lib/x86_64-linux-gnu/libparted.so.2(ped_disk_new+0x48) [0x7fab03000f18]
  9: /usr/lib/x86_64-linux-gnu/qt5/plugins/libpmlibpartedbackendplugin.so(+0x766b) [0x7faadce4366b]
  8: /usr/lib/x86_64-linux-gnu/qt5/plugins/libpmlibpartedbackendplugin.so(+0x81a0) [0x7faadce441a0]
  7: /usr/lib/calamares/modules/partition/libcalamares_viewmodule_partition.so(_ZN19PartitionCoreModule6doInitEv+0x49) [0x7faae4063a59]
  6: /usr/lib/calamares/modules/partition/libcalamares_viewmodule_partition.so(_ZN19PartitionCoreModule4initEv+0x1d) [0x7faae4064efd]
  5: /usr/lib/calamares/modules/partition/libcalamares_viewmodule_partition.so(_ZN12QtConcurrent15RunFunctionTaskIvE3runEv+0x75) [0x7faae4065555]
  4: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0xab14f) [0x7fab16b3c14f]
  3: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5(+0xaeda8) [0x7fab16b3fda8]
  2: /lib/x86_64-linux-gnu/libpthread.so.0(+0x7424) [0x7fab14cf0424]
  1: /lib/x86_64-linux-gnu/libc.so.6(clone+0x5f) [0x7fab162429bf]
Broken
Title: Re: Calamares fails big time.
Post by: devil on 2017/03/06, 13:36:46
We did a lot of internal testing before shipping the new installer, but what you described, never happened during out tests.  Could you please try to do a plain EN install and see if that works?

Maybe you also want to alter your headline, making clear, that this is true for you.
Title: Re: Calamares fails big time.
Post by: OppaErich on 2017/03/06, 14:38:25
Code: [Select]
siducer@siduction:~$ sudo calamares install -d
11:49:09 [1]: Calamares version: 3.1.0
Translation: Calamares: Using system locale: "pl_PL"
Translation: Qt: Using default locale, system locale one not found: "pl_PL"
...
11:49:09 [1]: Available languages: ("ar", ... , "pl", ... , "zh_TW")
Maybe that's all of it. Is Polish used in other countries than Poland ?
Title: Re: Calamares fails big time.
Post by: devil on 2017/03/06, 16:09:51
Marky,
I have talked to people from calamares and parted about this. They think, it might be an issue with your hard disk.
Can you run
Code: [Select]
smartctl -t short on the disk for starters?
Title: Re: Calamares fails big time.
Post by: marky on 2017/03/06, 17:49:17
Well, as the language is concerned for En I've got the same output as for Pl.

smartctl -t short doesn't work.

Code: [Select]
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART Short self-test routine immediately in off-line mode".
Drive command "Execute SMART Short self-test routine immediately in off-line mode" successful.
Testing has begun.
Please wait 1 minutes for test to complete.
Test will complete after Mon Mar  6 17:37:49 2017

Use smartctl -X to abort test.
[m@localhost ~]$


 So, I've used 'force':

Code: [Select]
[m@localhost ~]$ sudo smartctl -t force /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.0-514.10.2.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

ATA device successfully opened

Use 'smartctl -a' (or '-x') to print SMART (and more) information

Code: [Select]
[m@localhost ~]$ sudo smartctl -a /dev/sda
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.10.0-514.10.2.el7.x86_64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     PLEXTOR PX-256M6Pro
Serial Number:    P02444101104
LU WWN Device Id: 5 002303 10030d195
Add. Product Id:  NC802090
Firmware Version: 1.02
User Capacity:    256,060,514,304 bytes [256 GB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS, ATA/ATAPI-7 T13/1532D revision 4a
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Mon Mar  6 17:32:26 2017 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)   Offline data collection activity
               was never started.
               Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)   The previous self-test routine completed
               without error or no self-test has ever
               been run.
Total time to complete Offline
data collection:       (   10) seconds.
Offline data collection
capabilities:           (0x15) SMART execute Offline immediate.
               No Auto Offline data collection support.
               Abort Offline collection upon new
               command.
               No Offline surface scan supported.
               Self-test supported.
               No Conveyance Self-test supported.
               No Selective Self-test supported.
SMART capabilities:            (0x0003)   Saves SMART data before entering
               power-saving mode.
               Supports SMART auto save timer.
Error logging capability:        (0x01)   Error logging supported.
               General Purpose Logging supported.
Short self-test routine
recommended polling time:     (   1) minutes.
Extended self-test routine
recommended polling time:     (  10) minutes.
SCT capabilities:           (0x003d)   SCT Status supported.
               SCT Error Recovery Control supported.
               SCT Feature Control supported.
               SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x002f   100   100   000    Pre-fail  Always       -       0
  5 Reallocated_Sector_Ct   0x0003   100   100   000    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       4711
 12 Power_Cycle_Count       0x0003   100   100   000    Pre-fail  Always       -       2853
170 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       0
171 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       0
172 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       0
173 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       123
174 Unknown_Attribute       0x0003   100   100   000    Pre-fail  Always       -       112
175 Program_Fail_Count_Chip 0x0003   100   100   000    Pre-fail  Always       -       0
176 Erase_Fail_Count_Chip   0x0003   100   100   000    Pre-fail  Always       -       0
177 Wear_Leveling_Count     0x0003   100   100   000    Pre-fail  Always       -       125977
178 Used_Rsvd_Blk_Cnt_Chip  0x0003   100   100   000    Pre-fail  Always       -       0
179 Used_Rsvd_Blk_Cnt_Tot   0x0003   100   100   000    Pre-fail  Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   100   100   000    Pre-fail  Always       -       1856
181 Program_Fail_Cnt_Total  0x0003   100   100   000    Pre-fail  Always       -       0
182 Erase_Fail_Count_Total  0x0003   100   100   000    Pre-fail  Always       -       0
183 Runtime_Bad_Block       0x0032   100   100   000    Old_age   Always       -       0
184 End-to-End_Error        0x0033   100   100   000    Pre-fail  Always       -       0
187 Reported_Uncorrect      0x0003   100   100   000    Pre-fail  Always       -       0
188 Command_Timeout         0x0032   100   100   000    Old_age   Always       -       2
192 Power-Off_Retract_Count 0x0003   100   100   000    Pre-fail  Always       -       112
195 Hardware_ECC_Recovered  0x0003   100   100   000    Pre-fail  Always       -       0
196 Reallocated_Event_Count 0x0003   100   100   000    Pre-fail  Always       -       0
198 Offline_Uncorrectable   0x0003   100   100   000    Pre-fail  Always       -       0
199 UDMA_CRC_Error_Count    0x0003   100   100   000    Pre-fail  Always       -       0
232 Available_Reservd_Space 0x0003   100   100   010    Pre-fail  Always       -       0
233 Media_Wearout_Indicator 0x0003   100   100   000    Pre-fail  Always       -       31494
241 Total_LBAs_Written      0x0003   100   100   000    Pre-fail  Always       -       782385
242 Total_LBAs_Read         0x0003   100   100   000    Pre-fail  Always       -       995496

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      4711         -
# 2  Short offline       Completed without error       00%      4711         -
# 3  Short offline       Completed without error       00%      4711         -
# 4  Short offline       Completed without error       00%      4711         -
# 5  Short offline       Completed without error       00%      4711         -
# 6  Short offline       Completed without error       00%      4711         -
# 7  Short offline       Completed without error       00%      4711         -
# 8  Short offline       Completed without error       00%      4710         -

Selective Self-tests/Logging not supported
And my drives:
Code: [Select]
[m@localhost ~]$ lsblk -f
NAME   FSTYPE  LABEL                    UUID                                 MOUNTPOINT
sda                                                                         
├─sda1 ntfs    Zastrzeżone przez system 8E004FE7004FD4BD                     
└─sda2 ntfs    SSD                      0470D27D70D27540                     /run/media/m/SSD
sdb                                                                         
├─sdb1 ntfs    Magazyn                  01D21F1150195BF0                     /run/media/m/Magazyn
├─sdb2 ext4    BunsenLabs               d00f41ef-bdb2-466d-9461-b2aeb1d58ef8
├─sdb3 swap                             4bafb3e8-acb7-444a-b992-591e2afd0f18
└─sdb4 ext4    Fedora                   0cfdd477-438e-41ea-b3c8-55694fcf32a9
sdc                                                                         
├─sdc1 ntfs    Toshiba                  0534DAB15F9FB2B6                     /run/media/m/Toshiba
└─sdc2 ext4    CentOS                   00b00a40-33f6-4a99-966b-9d321af8113d /
sdd                                                                         
└─sdd1 vfat    CODEMETER                002C-6B2F                            /run/media/m/CODEMETER
sdf    iso9660 siduction                2017-03-05-18-54-54-00               
├─sdf1 iso9660 siduction                2017-03-05-18-54-54-00               
├─sdf2 vfat    siduction                1FEF-3D48                           
└─sdf3 iso9660 siduction                2017-03-05-18-54-54-00               
sdg                                                                         
└─sdg1 ext4                             596a4d58-8db6-4ce7-933c-87b64ab3da7b /run/media/m/596a4d58-8db6-4ce7-93
sr0                                                                         

BTW
There is no '[/code]' in your tool bar for code finishing.
Title: Re: Calamares fails big time.
Post by: marky on 2017/03/06, 18:07:00
Quote
Maybe you also want to alter your headline, making clear, that this is true for you.

- I'm not sure what do you mean by that.
Title: Re: Calamares fails big time.
Post by: marky on 2017/03/06, 19:17:53
Looks to me that calamares fails to get access to my hard drives having no space available for loading to memory

Code: [Select]

18:05:55 [1]: WARNING: cannot acquire a list of available locales. The locale and localecfg modules will be broken as long as this system does not provide  * a /usr/share/i18n/SUPPORTED file     OR  * a well-formed /etc/locale.gen     OR  * a complete pre-compiled locale-gen database which allows complete locale -a output.
....
18:05:56 [0]: void Calamares::Module::loadConfigurationFile(const QString&) bad module configuration format "/usr/share/calamares/modules/umount.conf"
18:05:56 [1]: LAST VS IS EVS!
18:05:56 [1]: ViewModule "finished@finished" loading complete.
18:05:56 [1]: STARTUP: loadModules for all modules done
18:05:56 [1]: STARTUP: Window now visible and ProgressTreeView populated
18:05:56 [1]: Need at least storage bytes: 5905580032
18:05:56 [8]: getting temp failed for  "/dev/sda" :  No such file or directory
18:05:56 [1]: Need at least ram bytes: 1073741824
Segmentation fault (core dumped)

And my recent Manjaro installation failure case confirms that problem with it.
At least for these SSD types disks.
'smartctl' command clearly confirms that as well.
Title: Re: Calamares fails big time.
Post by: devil on 2017/03/06, 19:37:28
What I mean by altering the headline is that basicaly you are saying: calamares does not work, where you should be saying: does not work for me. Other than that I am looking at your output later on.
Title: Re: Calamares fails big time.
Post by: marky on 2017/03/06, 20:17:20
Quote
What I mean by altering the headline is that basicaly you are saying: calamares does not work, where you should be saying: does not work for me. Other than that I am looking at your output later on



Actually, isn't that obvious that I post it personally?
But OK, I'll do that when they find a fault on my side, since I've seen several posts reporting similar problems with calamares on Manjaro and Netrunner forums.
What more, no other distros bring this type installation problems for me.


Cheers,
m
Title: Re: Calamares fails big time - for me.
Post by: marky on 2017/03/11, 21:55:01
OK, I've given a try one more time using Cinnamon desktop.
After maybe 20 clicks on installation icon - Calamares finally didn't disappear and caught as I could install Siduction.
I'm really pleased now as I expected from Debian based distro, fast, responsive, stable and really polished as for unstable release.
And what's amazing for me, installation took care already of my nvidia driver!.

Thank you guys, really good work!
Looks like I was s(i)educed by your distro on purpose and I'm not disappointed now.

BTW
I don't know how to change the headlines now as I'm not able to edit it.
So  you can do it yourself adding: 'for me' to the sentence.

Cheers,
m
Title: Zickig calamares fails here
Post by: mylo on 2017/08/13, 22:23:05
yes indeed zickig calamares starts 10 procs in top to see, but too lazy to do something.
with lxde in combi on an older pc difficult. problem seems to be with the disk or access thereto, although after reformatting hd calamares is not installing (update of apt, dpkg, perl and calamaris included).

screenshots to follow from an operating sid inst later

any hints?

Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/13, 22:42:49
screenshots to follow I made (aroung 200kB per=) but I gave up
dl as limit is 120 , so forget wasts my time
Title: Re: Calamares fails big time for me.
Post by: devil on 2017/08/13, 22:55:21
No hints without facts, sorry.
Title: Re: Calamares fails big time for me.
Post by: melmarker on 2017/08/13, 23:04:03
Wenns gar nicht anders geht, dann die Muttersprache benutzen - aber bitte keine Romane.
Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/13, 23:24:24
calamares stellt bei "JETZT INSTALLIEREN" vor aller Ehrfurcht die Arbeit ein; da passiert nix mehr.

Anscheinend wird die HD nicht richtig angefasst, ein funktionierendes Mint 16.* habe ich per format gekillt, aber calameres zeigt den gleichen Respekt. Das Angebot zum Formatieren ist unvollständifg. Werde mir noch einmal die Mühe machen, die Screenshots noch weiter extrem zu verkleinern (kommt ja hier auf jedes bit an; ich hatte die screenshots ja per handy machen müssen btw).
Gilt denn die 120 kbit Grenze hier pro Bild/attachment oder für alle drei Bilder?
Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/13, 23:29:28
mühsam 1von3
Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/13, 23:30:10
mühsam 2von3
Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/13, 23:30:36
mühsam 3von3
Title: Re: Calamares fails big time for me.
Post by: melmarker on 2017/08/14, 00:08:50
Zum Glück weiss ich fast nix über calamares - ausser dass man es eventuell aus dem Terminal aufrufen kann - so mit sudo. Und dann gibt das eventuell auch im Terminal nen sinnvolles Log. Die Bilder sind ja nett, mehr aber auch nicht.
Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/14, 01:15:29
hi melmarker,

mit sudo habe ich natürlich auch mehrmals durchprobiert, von kde vorher auch schon auf lxde, will aber nicht. scheint aber nicht (grundsätzlich) an der HW zu liegen, da da andere distros wie mint &co problemlos installieren und operieren.

macht nix, mache ich auf der kiste mit mint wieder weiter. schade, wollte harmonisieren, aber geht mit siduction nicht so..
Title: Re: Calamares fails big time for me.
Post by: melmarker on 2017/08/14, 02:23:54
Äh - ok - die Breitseite: Verdammt noch mal, wenn was nicht funktioniert, dann hat das einen Grund. Und diesen Grund würd ich gern wissen. Und dazu brauch ich logs und keine Prosa. Und wenn Du Dich mal im IRC melden würdest, dann könnte man da drüber sprechen und Du könntest ein ISO auf dem neusten Stand bekommen, in dem einige wesentliche Fehler - auch in Calamares - gefixt sind. Dat hat mich Tage gekostet um das nach Upstream zu bekommen :D

Is nich persönlich, aber ich hätte gern Logs, wenn was schiefgeht - nur um sicherzugehen, dass wir, wenn es denn wirklich ein Programmfehler ist, im nächsten Release eine gefixte Version anbieten. Und mit uns dann eventuell noch 15 andere Distributionen.
Title: Re: Calamares fails big time for me.
Post by: der_bud on 2017/08/14, 09:44:14
Nicht hauen wenn ich auch keine Logs etc anbiete :). Ich kann derzeit nur einen Hauch von CONFIRMED hinterherschieben, bin frühestens morgen Abend wieder in der Lage was zu machen:
Gestern auf Real Iron per grub2-fll-fromiso die siduction-17.1.0-patience-gnome-amd64-201708092324.iso  gestartet. In Calamres bis zu mylos erstem Bild mit der Partitionierung gekommen. In Unkenntnis was die Symbole bedeuten sollen gehofft, der fehlende Beschreibungstext ist "nur" irgendwie ausgeblendet. In eine freie Fläche geklickt (da wo in mylos erstem Bild der Mauszeiger ist), Calamares hat sich sofort sang-und-klanglos verabschiedet. Reproduzierbar mehrmals. Jetzt erst den Thread entdeckt, sonst hätte ich natürlich (!) Logs parat ;)
Und ja, ich weiß, das ist Prosa ohne Beleg, könnte aber vielleicht Andere dazu animieren mit aktuellem Iso mal eine echte Installation zu testen...

Screenshot mit calamares und inxi  http://paste.siduction.org/20170813172217.jpg
Title: Re: Calamares fails big time for me.
Post by: devil on 2017/08/14, 14:09:26
Die Bildchen im Screenshot von derBud sind befremdlich, hab ich so noch nie gehsehen. Hatte immer Text. Ich habe vor wenigen Tagen eine Installation mit dem letzten offiziellen Release (Patience) auf ein Tuxedo InfinityBook 13 Pro v2  gemacht und hatte keine Probleme. Ich habe allerdings auch nicht (und noch nie mit Calamares) die mauelle Partition gewählt, sondern 'Ersetze die bestehende Installation' oder so ähnlich. Ich werde das nachher noch mal neu machen und Bildchen machen.
Title: Re: Calamares fails big time for me.
Post by: piper on 2017/08/14, 14:26:51
I can confirm on 3 different machines with calamares in the "partition" section.

All 3 machines show the same results (custom & stock builds)     

"Storage device" under manual partitioning shows no partitions at all, there is no dropdown to select where you want to install to.
Title: Re: Calamares fails big time for me.
Post by: devil on 2017/08/14, 15:14:51
Just did an install with Patience as it is (nothing updated before install). All options incl. manual partitioning work fine and the installation worked fine as well. Will do another install with updating Cala before install and report back later today.
Title: Re: Calamares fails big time for me.
Post by: piper on 2017/08/14, 16:24:41
Some screenshots and 2 logs

https://goo.gl/photos/ZBf2JRg7PWLdSqBW7
https://goo.gl/photos/sHPQFnvHGG7P6Xi99
https://goo.gl/photos/ko3M7izd3hH4U84u5
https://goo.gl/photos/rxfMmrVn5U7JtdcW9

http://paste.debian.net/hidden/7d321a27/

I have tried builds locally, one stock, one my custom, and one from the build server itself.


cli-installer works, not a fix or solution, but, if really need to install because system is borked, it works
Title: Re: Calamares fails big time for me.
Post by: melmarker on 2017/08/14, 17:12:52
@piper - please provide the used iso - aka iso name/download path thanks
Title: Re: Calamares fails big time for me.
Post by: piper on 2017/08/14, 17:26:47
@melmarker - the last one built on the build server, which matches the one shown in the inxi screenshot (201708141249)

https://ci.siduction.org/view/20%20PATIENCE/job/Build%20Patience%20KDE%20amd64/lastSuccessfulBuild/consoleFull

https://isobuilds.siduction.org/kde/amd64/siduction-17.1.0-patience-kde-amd64-201708141249.iso

My local builds build, but fail to show any drives in partitioning when it comes time to install, same as the build server build
Title: Re: Calamares fails big time for me.
Post by: piper on 2017/08/14, 18:19:30
Some weird shit, works in vbox

(http://pipersid.net/myshit/linux/images/thumb-vbox1.png) (http://pipersid.net/myshit/linux/images/vbox1.png)

(http://pipersid.net/myshit/linux/images/thumb-vbox2.png) (http://pipersid.net/myshit/linux/images/vbox2.png)

Title: Re: Calamares fails big time for me.
Post by: melmarker on 2017/08/14, 19:00:16
hihihi :D

ok, not so funny, but at least not boring - could you please try our latest (kde) release the same way?
Title: Re: Calamares fails big time for me.
Post by: mylo on 2017/08/14, 20:07:46
piper wrote:
Code: [Select]
"Storage device" under manual partitioning shows no partitions at all, there is no dropdown to select where you want to install to.
+1

I had the same experience, in option "manual partitioning".
I updated
Code: [Select]
perl calamares apt dpkg. However I am not sure, whether such an update takes effect at once, so without rebooting, which is no option on a running live-cd.

I will be in irc tonight, may be I can test and provide logs from that machine, when you tell me what you guys want. I think, I can extract them by an usb stick over to my first machine in order to bring it to irc.
Title: Re: Calamares fails big time for me.
Post by: piper on 2017/08/14, 20:42:15
There is a problem here, the problem is me

This is the KDE release iso,,

siduction-17.1.0-patience-kde-amd64-201703051755.iso

this, I have no problems with, all works as it should

Ignore my post above, those are new builds, not for release :(
Title: Re: Calamares fails big time for me.
Post by: devil on 2017/08/15, 09:09:12
Calamares probably needs a rebuild due to many changes in the last few months. The version on the release images works fine.
Title: Re: Calamares fails big time for me.
Post by: bevo on 2017/08/17, 13:37:54
Calamares probably needs a rebuild due to many changes in the last few months. The version on the release images works fine.

Is there a version which supports LVM yet?
Title: Re: Calamares fails big time for me.
Post by: devil on 2017/08/17, 19:26:14
You need to create the LVM Volume beforehand, then it should work. Not tested it myself though.
Title: Re: Calamares fails big time for me.
Post by: bevo on 2017/08/17, 21:22:45
Does not work, problem as described.

https://forum.openmandriva.org/t/does-calamares-support-lvm2-volumes/632 (https://forum.openmandriva.org/t/does-calamares-support-lvm2-volumes/632)

So I will wait  ;)

Title: Re: Calamares fails big time for me.
Post by: melmarker on 2017/08/17, 23:14:40
i guess there are no plans to implement lvm2 in the next future - at least i don't know nothing about.
so installing with calamares to a normal partition and transfer to lvm should work