October 2015 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] Boot of iso image on USB stick with Tumbleweed on Dell Lattitude E5500 failed
by Freek de Kruijf 30 Oct '15

30 Oct '15

I tried to boot from a USB stick on which I wrote the iso image of the latest Tumbleed 20151022 using SUSE Studio Imagewriter on a Dell laptop Lattitude E5500. Obviously I rearranged in the BIOS to start looking for a bootable image from a USB device. The laptop did not see a bootable image on the USB stick and started from the hard disc. I searched the Internet for a solution, but did not find one. Anyone succeeded in installing openSUSE on this laptop? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 8

[opensuse-factory] openSUSE Leap GM: KDE crash at very start
by opensuse.lietuviu.kalba 30 Oct '15

30 Oct '15

Hi, Just tested openSUSE 42.1 GoldMaster installed in VirtualBox 4.3.32 Default installation parameters used, selected to include additional repos, like non-OSS updates, debug-info (i.e. no custom repos). Just after install started KDE Plasma 5 crash. Total 3 crash dialogs appears in black screen. Desktop will not show at all. https://bugzilla.suse.com/show_bug.cgi?id=952850 -- Regards, M -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 3

[opensuse-factory] Booting problems with Tumbleweed
by C. Brouerius van Nidek 30 Oct '15

30 Oct '15

Since several updates I have problems with the boot process. In most cases the process stops just before my screens should show up. Sometimes nothing shows, sometimes some programs show and than freezes. CtrlAltDel will not work but I can always logout with Ctl Alt <-- After trying several times to reboot from the init 3 position sometimes with success. I also have to retreat to a complete reboot. . I am using Plasma. If I choose LXQT I have no booting problem whatever. I am planning to find out what my problem is and have started reading xsession-errors, kdm.log, boot.log and such. Ran rpmbuilddb followed by rpm -Va '*' but this search brought me not much closer to my goal to get a smooth booting Tumbleweed. Is there some site with instructions? Other suggestions? -- Linux User 183145 using KDE4 Tumbleweed on a Pentium IV , powered by openSUSE 20151022 (x86_64) Kernel: 4.2.3-4.g549889b-default KDE Development Platform: 4.14.12 14:35pm up 5:48, 3 users, load average: 0.18, 0.30, 0.51 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 2

Re: [opensuse-factory] dumbfounded by Enlightenment
by Felix Miata 29 Oct '15

29 Oct '15

Simon Lees composed on 2015-10-29 20:43 (UTC+1030): > Sorry for the late reply i'm the openSUSE maintainer in my spare time > and some weeks I don't get to checking this list that quickly and the > high volume of traffic in the last week hasn't helped. I am not a > regular enlightenment developer although I do submit occasional patches. > Given alot of enlightenment developers are in similar enough timezones > to me I spend a reasonable amount of time chatting to them on IRC so I > can answer most of your questions. > I guess I should start by confirming your running the enlightenment > package rather then e17, given you mentioned Leap I will presume so. > Firstly I would recommend trying the software renderer which in > enlightenment is exceptionally good, it runs well on the well over 5yo > Athlon Turion X2 i'm writing this email from it also runs pretty > reasonably on my ODroid C1 (rpi clone) to enable it "Settings -> > Composite->Rendering" In that dialog you can also disable effects which > may help. Unfortunately there has always been performance issues with > that Card / driver combo. > The comment that compositors are slow is a common misconception brought > about firstly by compiz and possibly added to by kde and gnome, > benchmarking was done when enlightenment went compositor only and it > found that the compositor didn't add significant performance decreases. > By making the compositor a hard requirement a lot of code paths were > rewritten to be much simpler which reduced alot of bugs. But the key > driver was wayland, e20 which will be released in the next couple of > months will ship with full wayland support including xwayland, in order > to work with wayland you need to have a compositor and the enlightenment > devs believe that wayland will be the future hence there focus here. > It is well known that the enlightenment configuration dialogs are a mess > they have slowly evolved over 15 years without a huge amount of thought, > now that wayland support is there rewriting all the config dialogs is > the main aim for e21 which will hopefully be around for openSUSE Leap 42.2 Bad config dialogs amount to a blocker for me. I'm too old to deal with this kind of usability obstacle. Functionality is far more important than visual appeal here. > As for themes the enlightenment theme engine is incredibly powerful and > flexible unfortunately that also makes it incredibly complex it would > probably take atleast a month full time work to develop a completely new > theme, given that the widget set in enlightenment has only really been > stable for the last 2 years themers are only just starting to catch up. > Jeff Hoogland from the bodhi Linux team has just got a couple of themes > mostly complete and a couple of others are starting to spring up so > expect 42.2 to have a much better theme selection, thats going to be my > aim for the next release. The main thing I spent time on last release > was backporting app indicator systray support into the version of > nm-applet that ships with openSUSE so that for the first time openSUSE > users have some form of network manager integration in enlightenment. I've nearly always managed to be content with default upstream theming. Ignoring DOS and vtty shells, I don't recall ever encountering a dark upstream default before. I strongly favor things being workable out of the box. For me, light on dark does not work. > If you would like a lighter theme try installing > enlightenment-theme-openSUSE-ice it does still have the 13.2 branding > which is mostly because I couldn't make a light theme look good against > a wallpaper thats almost all black. I also have some scripts for > customising themes if you want to try > http://simotek.net/tech/projects/opensuse-e/darkmod-enlightenment-theme-con… > Personally I am working on a new theme > https://pbs.twimg.com/media/CCO3pKdUkAAs_sQ.jpg:large Both of those URLs are typical examples of why some people hate using computers and/or the web. Everything is painfully tiny by default. It causes the proverbial chicken/egg situation. Tools may or may not exist to undo tiny, but because even when they exist they're tiny, they're unusable in solving the too-tiny problem. Taking the dialog on first open of E as example, it's good in that it wants to make it easy to correct to sizing problem, bad in the starting base being smallest possible selection. It's far easier for a user who wants smaller to downsize than it is for a user who needs larger to upsize. The developer population is obviously thinly populated by those who have worse than average vision. People with trouble seeing tend to be drawn to occupations where sitting in front of a computer screen most of the time is not part of the job description. Thus, developer vision overall is better than average, and more than just a little bit, leading to smaller being OK or even standard, which in turn leads to more objects fitting into any given design space. That in turn leads to trouble for those who need bigger objects. Spaces become too busy, crowded, not uncommonly to the point of total obstacle to usability. > As for resizing windows the easiest way is holding down the Win key and > using left click and drag you can also grab the bottom corners of the > windows and click and drag but the bottom window border is rather small, > something i've never liked. Dependance on Win keys amounts to another killer for me. I've not found a satisfactory keyboard to have been made in over two decades.[1] Every satisfactory keyboard I've ever seen was made before Win keys first appeared. > If you need any more help I tend to get to reading this list eventually > and am generally on irc during my business hours and some evenings GMT > +10:30 otherwise there is very helpful people in #e, #opensuse-e and > enlightenment-users(a)lists.sourceforge.net > Thanks for the feedback It appears there's no point in my pursuing E. Had I seen this little bit from Wikipedia Enlightenment developers have referred to it as "the original eye-candy window manager". I wouldn't even have tried it. I do appreciate the time you took to reply. [1] Examples of satisfactory keyboards can be seen here: https://en.wikipedia.org/wiki/Northgate_Computers#/media/File:Omnikey102p32… https://commons.wikimedia.org/wiki/File:ErgoLogicFlexProKB2652.jpg -- "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-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] WARNING: Renaming 'openSUSE Factory' in Bugzilla
by Richard Brown 29 Oct '15

29 Oct '15

Hi All, I'm about to rename 'openSUSE Factory' in Bugzilla so it reads 'openSUSE Tumbleweed' This is for the obvious reason so people know where to file bugs they find with Tumbleweed The system is warning me that once I commit this change "** If you modify the name, all Bugzilla URL links will be broken! **" The only obvious links I can think of are on the wiki https://en.opensuse.org/openSUSE:Submitting_bug_reports I will fix these links when the change goes live But if you have any of your own bookmarks or saved links to Bugzilla that reference the 'openSUSE Factory' product name, please replace Factory with Tumbleweed once this goes live at approximately 5PM Berlin Time today Regards, Richard -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

Re: [opensuse-factory] no kernel-desktop?
by Dmitriy Perlow 29 Oct '15

29 Oct '15

Hartmut Rosch <hartmut.rosch(a)ewetel.net> Thu, 29 Oct 2015 20:58:15 +0300: Hello. > Did I miss a notice saying there is no kernel-desktop? Yep: http://lists.opensuse.org/opensuse-factory/2015-10/msg00330.html -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] KF5: kdevelop is missing drkonqi
by Hartmut Rosch 29 Oct '15

29 Oct '15

Hello, I just updated from rev. 13.2 to tumbleweed. It doesn't work as I expected but with plasma5 it should show differences. For my more or less privete developing work i am using kdevelop quite often. And with KDE4 it worked well. Now after the upgrade to tumbleweed it crashes when kdevelp is calling drkonqi. It looks like that kdevelop is calling kdeinit and after that drkonqi fails to start. I am attaching a crash.txt which reports the crash -- greetings Hartmut Rosch Delmenhorst -----------

3 3

[opensuse-factory] Help with OBS message
by Larry Finger 29 Oct '15

29 Oct '15

Hi, I got E-mail from OBS Notification that "Package openSUSE:Factory/virtualbox failed to build in standard/i586". The results are at https://build.opensuse.org/package/live_build_log/openSUSE:Factory/virtualb… There are some warnings in those messages, but I do not see any errors, or any other indication as to why the build failed. Could some expert in OBS and/or RPM building give me a clue. I think the x86_64 build, which uses the same spec file, completes without any problem. Thanks, Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 4

RE: Re: [opensuse-factory] New Tumbleweed installation: when grub2 password set, user root and grub password asked at every boot
by stakanov＠freenet.de 29 Oct '15

29 Oct '15

This is a fresh install of the latest snapshot of TW with password protected grub and Luks LVM. No gimmicks other than this modified or set. So this does not work, at least if the BIOS is not UEFI but an older Award BIOS. I checked and that option to allow boot if no parameters are altered is already set. I did unset it and reset it and safed. Still it askes for password of grub2 or it will not boot. There are two possibilities: a) bug in grub b) malware in the usb-firmware setting a boot parameter before starting up the system. History behind that: I have had a very strange behavior of the keyboards of my PC. I had originally a MS keyboard on this system with former installation but after loading the kernel I would never been able to input my luks password (if it was not with the MS keyboard used at install, e.g. a Cheery keyboard was seen and working up to the kernel was loaded than practically without function). That raised in me the doubt that something emulated the keyboard. Even more so because I had the very same behavior before on my notebook. On that notebook after inserting an USB key of untrusted source, my password in a CLI for root suddenly echoed, my system was blocking and I found rcp-bind listening permanently and persistent on port 111 to the www. The keyboard would not work anymore on the docking station after a kernel upgrade while the notebook keyboard did. (While the usb-key in question was used only once on the notebook w/o dockingstation. That famous foreign usb-key did not mount as expected in opensuse. Actually, it did not mount at all because in secure mode, the pop-up asking root to mount it was never appearing. Hence I gave it a try with a new install from scratch by formatting all the HDD and then giving it a try. This very USB-key I did use it also on my PC afterwards (because I was rightly not knowing about a potential problem with USB. Long story short, that's all fishy to me and I would like to be sure not having "little green men". In the light of the bad-usb story (which can be apparently programmed by whatever script kiddy), how can one check if an unwanted boot parameter has been passed to grub while booting up? Or does journalctl document such parameters somewhere? BTW, i am also getting while booting the system now the following error message in my logs that I sincerely do not understand: from "journalctl -r". AFAIK I do not have an fstab in Tumbleweed from the scratch. Oct 29 09:19:25 linux-e3dj systemd[1]: Started Reload Configuration from the Real Root. Oct 29 09:19:25 linux-e3dj systemd[1052]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with error code 1. Oct 29 09:19:25 linux-e3dj systemd-fstab-generator[1055]: Failed to create mount unit file /run/systemd/generator/sysroot.mount, as it already exists. Duplicate entry in /etc/fstab? Sorry for being paranoid but to a certain extent I have reason to be. If it is just a bug in grub, I am cheerful and everybody is happy to have found one, to report and correct, right? :-) As it is, it is really annoying to have to put in the user "root" and the password of Grub every boot. > -----Ursprüngliche Nachricht----- > Von: Andrei Borzenkov > Gesendet: Do. 29.10.2015 09:05 > >> I did set passwordprotected grub, but > I was used to the behavior that you are asked the password only > if > you set supplemental boot parameter. Has this changed? > > There should be "Allow to boot locked default entry without password" > option. > >> Why am I asked for the "user". Isn't > it expected by default that it is root? > > yast-bootloader creates password for user root. But GRUB has no way > to > know, if you want to authenticate yourself as user "root" or any > other > user. > -- > > -----Ursprüngliche Nachricht Ende----- --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] New Tumbleweed installation: when grub2 password set, user root and grub password asked at every boot
by stakanov＠freenet.de 29 Oct '15

29 Oct '15

Is it normal that I am asked at a promt at every boot "enter user", enter password - signifying user root and password of the grub2? I did set passwordprotected grub, but I was used to the behavior that you are asked the password only if you set supplemental boot parameter. Has this changed? Why am I asked for the "user". Isn't it expected by default that it is root? Or can i attribute this responsibility also to one of the group "users" or to a group e.g. "wheel"? Thank you --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1