On Fri, 2015-08-14 at 20:33 -0300, Ronan Arraes Jardim Chagas wrote:
Dear Dominique,
Em sex 14 ago 2015, às 16:20:10, Dominique Leuenberger / DimStar escreveu:
The most important changes were: * GParted 0.23 update (mainly interesting for GPT) * Libreoffice was pushed to 5.0.0.5, getting you some fixes * Mesa 10.6.3 (fixes crashes when playing videos in VLC with vdpau) * Firefox 39.0.3 (security fixes over 39.0) * BIND 9.10.2P3 (Security fixes) * CMAKE was bumped to 3.3; for once, it was painless * Linux kernel 4.1.4
To our knowledge, is is now finally again possible to put the Tumbleweed ISOs on a USB Stick and boot from it in UEFI environments. Some users seem still to have issues, but those have a different cause; those users also experience issues after updating an existing TW installation; the cause is not yet known
I tried to install Tumbleweed in UEFI system from the ISO on a USB stick. Now, it seems that I can boot into the installation. However, when the partitions are read, then YaST crash. I managed to install Tumbleweed by upgrading from openSUSE 13.2. But it turns out that if I open disk module of YaST, it also crashes with the same error, which is:
Run command: /sbin/yast2 disk & terminate called after throwing an instance of 'storage::SystemCmdException' what(): parted complains: Warning: failed to translate partition name: "/usr/sbin/parted -s '/dev/sda' unit cyl print unit s print" YaST got signal 6 at file /usr/share/YaST2/modules/ProductFeatures.rb:170 /sbin/yast2: line 434: 18463 Abortado $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS
That's an entirely different bug - please report it, if you can't find anything in bugzilla (I'm not aware of any such bug so far)
P.S.: By the way, the upgrade from 13.2 to Tumbleweed initially gave me a kernel panic The problem occurred when apparmor-abstraction was updated. I fixed by disabling apparmor before `zypper dup` by `systemctl stop apparmor`. Another guy in this spanish forum: http://www.forosuse.org/forosuse/showthread.php?t=32755 also had the same problem. Again, is it a known bug or should I report it?
Search in bugzilla for apparmor an if you can't find anything looking
to be the same, report it...
--
Dimstar / Dominique Leuenberger