November 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] LEAP 42.1 Problems with aaa_ package and Eclipse
by Johannes Weberhofer 18 Nov '15

18 Nov '15

Hello! Some days ago there was an update in the aaa_ packages. This update causes Eclipse Mars 4.5.1 no longer able to open network-connections (for updates, installing packages etc.). I have now rolled back to the original rolled out with Leap which solved those problems. I liked to report the bug to https://bugzilla.opensuse.org/ , but there is no Leap 42.1 product available to be selected. Hope, somebody can help out here. Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] Leap and ZYPP_MULTICURL=0
by Roger Oberholtzer 18 Nov '15

18 Nov '15

Does anyone know if zypper in Leap supports ZYPP_MULTICURL=0 ? I ask because I am trying to update a system where I have needed this in the past, and I think it looks like it is exhibiting the same behavior as when this option is not used. I would at least like to eliminate that as a source of problems for zypper downloading RPMs. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 15

[opensuse] Went to Kubuntu for some time
by Albert Oszkó 18 Nov '15

18 Nov '15

Hi all, As I mentioned a week or so ago, I installed Leap/KDE on Lenovo G505. I could hardly wait Leap, because I had to make too much compromise with 13.2, so I hoped things can only get better. Well, they did not. The installation went flawlessly, but then I tried to use the machine, and there were several severe problems. Not with the look of the desktop, it is mainly a matter of taste - but I admit it can also has an effect on usage. The nerve-cracking behavior of KWallet can somehow be tamed. But the continuous crashes of LibreOffice was showstopping. I uninstalled, the installed 5.0.3 - get the same crash. Looks like starting Writer, Calc, etc made the system log out. The common start menu of Libre worked, but the individual parts did not. Finally I reinstalled Leap. The Libre complained that somebody (that is me) from the previous installation edited something. So I deleted libreoffice from /home/.local. I removed my earlier persona, but did not remove crashes. So I considered giving a try to Linux Mint 17.2 with MATE. Could not install it. ( I disabled UEFI and Secure boot). Ubuntu 15.04 installed like a charm and upgraded to 15.10 - with kernel 4.2. I did not like it, could not import my client.ovpn file, and found ridiculous that it has no scanner support per se. So I installed Kubuntu 15.10 - and all things work. I got used to Suse - started with 9.1, and want to go back after changing this laptop. The reason I wrote this long text is that I am absolutely lost in the reasons of crashes. Nobody tells Libre5 crashes on Leap - neither on the libreoffice list. So I thought the mistake is on my side. And yet, *buntus with 4.2 kernel work. Do you have an idea what is wrong with this Leap install? Please let me share a final thought in a different topic. I am eager what Suse guys think of the future of this distro. I mean Leap came out only in 64 bit version. I think there are thousands of elder 32 bit machines still working. The other day I met one not accepting even 13.2 with ext4 filesystems. They will look after another distro when they want some more recent system. Best regards, Albert -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

15 31

RE: [opensuse] Leap 4.2 Log in Problem
by stakanov＠freenet.de 18 Nov '15

18 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Richard > Gesendet: Mo. 16.11.2015 19:16 > An: opensuse(a)opensuse.org > Betreff: [opensuse] Leap 4.2 Log in Problem > > > I have tried to install Leap on my Gigabyte GA-B8M-D3H machine. In > the > past the only distros I was able to install and use were Windows 8.1 > (a > lemon), Windows 10 (somewhat better) and recently the latest > iteration > of Ubuntu - 15.4, 15.10, and their close relatives. > I have tried both Tumbleweed and 13.2 without success but neither > will > install. It seems only those distros with the 4+ kernel will install > on > my motherboard. > I downloaded Leap and got it installed but can get no further than > the > log-in screen because this cycles -loops. Leap is installed but there > > appears to be a gilcth/bug in the log-in screen. I re-installed it > several times varying the log-in screen settings with the same > results. > I have Gooled the problem but Leap is too new for any usable results. > I hope this is enough info for some of you gurus to suggest a > solution > or work-around. > Thanks in advanced > unclerichard > > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- If you did install 13.2 you did install a 3.7 kernel. If you did install Tumbleweed from the current snapshot, you did install kernel 4.3. If you did have problems with both that indicates that your machine has no problem to install these kernels at all but that there is probably a totally other issue. Gigabyte Mainboards are not really to be called Linux friendly. Sometimes they have hickups. For what is you problem, I do not understand what you say. What is exactly the "login screen" for you? Do you have more than one user, do you have automated login and it blocks while loading plasma? When you press Escape during the loading process, do you see any error message? What graphics card do you run? Intel? Try to start with the boot parameter NOMODESET Does that help? (Do you know how to put boot parameter?). --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

RE: Re: [opensuse] Leap 4.2 Log in Problem
by stakanov＠freenet.de 18 Nov '15

18 Nov '15

> -----Ursprüngliche Nachricht----- > Von: Basil Chupin >. > > I always buy Gigabyte motherboards (and always use AMD cpus) and have > NEVER found Gigabyte m/boards to be not friendly to Linux distro of any > flavour. > > Dear Basil. I would say that the latter sentence was the (maybe) only useful sentence of that post. All the rest does not seem a contribution. For what is your personal experience (that is, you and only you) I am happy that you did not have problems with Gigabyte. What this helps with the OP of the person seeking help...I do not know. What does this contradict what i did say: nothing. What this says about Gigabyte and Linux? Nothing. Gigabyte had recently several main-boards with incompatibility of the USB3 Chipset and some severe UEFI trouble. You need to switch on IOMMU and still you will get a continuous spamming of the kernel while booting anyway. The USB3 will not function correctly anyway. The 32bit version of Linux is not hit by this, so if you are using Gigabyte and 32 bit, you personal experience do not join anything to the post you are referring to. Especially as Leap exists only for 64. Contacted by me about the issue Gigabyte responded that they do not see any issue because "Windows works fine" and they do not support Linux in any way. (In other words: we do not give a FF) AND they are not new in recent times to abandon one MB revision over an other with half-baken UEFI BIOS without any update (hanging in beta and giving only AGESA updates when they have to because of exploits, lacking translations...a mess). I am talking about the AMD AM3+ platform, if you are Intel YMMV, although I doubt it. So my advice (by personal experience and if you google about gigabyte, linux, problem you will find) I would rather use Biostar or Asus with Linux. Ashrok by itself was not bad but had in my case build in "vista" specific crapware that makes that in the end "you get what you pay for" so better Asus. Oh, with 5 mainboards used personally only the 939 boards and AM2 where still of quality. Breakages have been much more frequent than expected. So fare about "ultra durable" claims. If you then have some advice to give to our friend in trouble here, please go ahead. All other things would be "hijacking a thread" that "may" still be useful should the O.P. come back here. If not have a good day, "expert". ;-) Cheers. P.S. This may come over "harsh", it shouldn't. if you wish to have an exchange over Linux Hardware compatibility, please feel welcome to open a new thread so people may exchange their experiences. May well be of interest (although I do not know if this would not be bullied by somebody being "waste of lines" or whatever. Concerning the latter, the recent usage of this list makes me wonder about the validity of such statements). --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] RAID1 13.2 clone via rsync could not find /dev/mdX root device
by Felix Miata 18 Nov '15

18 Nov '15

CPU is Intel Haswell on B85 chipset. Multiboot RAID1 installation started with 13.1 on /dev/md1, 11.4 on /dev/md2, and 13.2 on /dev/md3. Wishing to test a DVD media upgrade from 32 bit to 64, booted to 13.1, I umounted 11.4 (on EXT3), reformatted md2 EXT4, remounted md2, then rsync'd from 13.2 on md3 to the freshly formatted md2. Next I adjusted what was the 11.4 grub stanza on /dev/sda1 to do the new 13.2 on md2, and fstab on md2. When I tried to boot md2, I always got a Dracut emergency shell reporting [/dev/md2|LABEL=10os13264] root device does not exist. After a few repeats, I booted the original 13.2 on md3, chrooted into the new 13.2 on md2, changed dracut's configs to hostonly="no" and hostonly_cmdline="no", ran dracut, and tried booting 13.2 on md2 again, with identical result, except taking 6+ seconds instead of 4+ seconds to reach the fail point due to the monstrously larger non-hostonly initrd. The dracut shell seems to be produce a runaround trying to mount anything to copy rdsosreport.txt to. It has no fdisk to report anything about partitioning. /dev/md* does not exist. 'systemctl reboot' apparently won't complete, as it's trying to undo things that it failed to do in the first place. CAD doesn't do anything. 'exit' doesn't cause reboot either. Finally I tried another chroot initrd build, this time with hostonly='no', and with add_drivers+="raid1 md_mod". It works, but I don't understand why the explicit addition of the two extra modules to the initrd was required, or why the failure with the comprehensive hostonly=no initrd. If this kind of clone can't be booted without all the fuss, how could a restored backup? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] i586 Tumbleweed Installation ISO Has x_86_64 image files
by Maitreya Maziarz 17 Nov '15

17 Nov '15

Hello, Trying to install openSUSE Tumbleweed from the 20151111 i586 snapshot, I get an error that common-base-i386.tar.xz is not found on the medium. Examining the contents of ~/images/ I note all the files are x86_64. I also downloaded 20151113, and it has the same issue. Am I doing something wrong, or was there an error made while compiling the snapshot? Thanks! --Maitreya -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] SLiM in Leap 42.1
by Alex Naumov 17 Nov '15

17 Nov '15

Hello, does anybody know which argument should be used to start SLIM as a login manager? /etc/sysconfig/displaymanager DISPLAYMANAGER="" Thank you, Alex -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

RE: [opensuse] bug? network installation leap 42.1 sha256sum file chrashes leap42.1 system
by stakanov＠freenet.de 17 Nov '15

17 Nov '15

> -----Ursprüngliche Nachricht----- > Von: tobi > Gesendet: Di. 17.11.2015 13:45 > An: opensuse(a)opensuse.org > Betreff: [opensuse] bug? network installation leap 42.1 sha256sum file chrashes leap42.1 system > > Hi, > > I'm new to opensuse and hope I'm on the right list now. (I wanted to > report a possible bug and was adviced by the website to ask on a list > first). > My problem is as follows: > > I'm running opensuse leap 42.1. I like it and also want to install it on > my netbook. I downloaded the network-installation iso. > now, when I'm trying to verify the data and open the following file: >http://download.opensuse.org/distribution/leap/42.1/iso/openSUSE-Leap-42.1-… > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- I think the easiest would be to use the gpg --verify to check the integrity If there is a bug with the checksum, with gpg you can be even saver and ship around it. If the file is compromised, gpg --verify will reveal it. I guess you know where to get the checksum (easy was alway, I found to go the download page and take "choose mirror" which then opens a page where gpg checksum as well as sha sums are all there). --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Leap and software update checking
by Roger Oberholtzer 17 Nov '15

17 Nov '15

In Leap/Plasma5, checking for software updates is enabled by default. When clicking on SoftwareUpdates->SoftwareUpdatesSettings, the Check Interval can be set to Daily, Weekly or Monthly. But I don't see where it can be disabled. Call me silly, but such a setting (e.g., Never) would logically be part of these settings. But is it set somewhere else? Or is it just missing? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2