February 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Btrfs ...
by Dr.-Ing. Dieter Jurzitza 30 Mar '17

30 Mar '17

Dear listmembers, dear openSUSE - maintainers, I maintain about 5 to 6 PC running (openSUSE) linux. My own, my sisters my friends ... Currently most of them are running with leap. During the last month I had to reinstall _all_ of them. All with broken / inconsitent / strange behaving root Btrfs file systems. After 25 years of working with linux I'd consider myself kind of experienced what regards linux problems. And, if that had had happened once I would have said it has been my fault. I do not think so any more. I consider Btrfs instable and inappropriate for public usage. I'd go further and would like to ask, *why* this is set as the default root fs when installing. This is totally inunderstandable to me after my experiences. I never ever experienced any bit of advantage in comparison with ext4. But I experienced nights of work - just to restore a state that had had existed a few days before. So, please, think it over: *take Btrfs out as default!* Use stable and well known systems as the foundation of public systems. Changing things only to change something is leading nowhere. Besides, if there is a kind soul that can explain what was the reason for making Btrfs the default I would highly appreciate. I cannot see any change besides significantly improved stability when going back to ext4. The latter being the most important thing IMHO. My two cents regards Dieter Jurzitza -- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

20 123

[opensuse] leap42.1 - how do I get the hostname displayed on the GUI login/lock screen?
by Per Jessen 17 Mar '17

17 Mar '17

$SUBJ says it all - I'm missing the hostname. When several PC are connected via a kvm switch it's handy being able to tell where you are logging in. -- Per Jessen, Zürich (4.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 42

[opensuse] smbclient issues
by Roger Oberholtzer 08 Mar '17

08 Mar '17

I have two openSUSE machines that have joined the same Windows domain. Both have done this via yast. The 12.3 machine has no trouble verifying users against the domain. The Tumbleweed machine, however, fails. On the openSUSE 12.3 client where it works, I get something like this: smbclient --user=roropq //os12p3/roger WARNING: The "idmap gid" option is deprecated WARNING: The "idmap uid" option is deprecated Unknown parameter encountered: "mangle case" Ignoring unknown parameter "mangle case" Domain=[RAMBOLL] OS=[Unix] Server=[Samba 3.6.12-59.23.1-3256-SUSE-SL12.3-i386] smb: \> On the Tumbleweed machine, I see this: smbclient --user=roropq //Tumblereed/roger WARNING: The "idmap gid" option is deprecated WARNING: The "idmap uid" option is deprecated Unknown parameter encountered: "mangle case" Ignoring unknown parameter "mangle case" Domain=[RAMBOLL] OS=[Windows 6.1] Server=[Samba 4.5.3-0-SUSE-oS13.3-x86_64] tree connect failed: NT_STATUS_ACCESS_DENIED It is interesting that the 12.3 samba reports the OS as Unix, while the Tumbleweed samba reports as Windows 6.1. The Server strings match the installed Samba on each machine. When yast checks that the machine is a member of the domain, it is happy. And the domain admin sees both machine as expected (by him). The two machines, as far as I can tell, have samba configured the exact same way. I see this in the samba logs: [2017/02/09 13:42:51.306927, 0] ../source3/libads/kerberos_util.c:74(ads_kinit_password) kerberos_kinit_password STO-OPQ-SRC$(a)RAMBOLL.RAMBOLL-GROUP.GLOBAL.NETWORK failed: KDC has no support for encryption type I have googled this, but I cannot say that I have seen anything that makes sense in the context of samba. This is a bit outside my experience. FYI, the configuration for both machines is: [global] workgroup = RAMBOLL passdb backend = tdbsam printing = cups printcap name = cups printcap cache time = 750 cups options = raw map to guest = Bad User include = /etc/samba/dhcp.conf logon path = \\%L\profiles\.msprofile logon home = \\%L\%U\.9xprofile logon drive = P: usershare allow guests = No idmap gid = 10000-20000 idmap uid = 10000-20000 realm = RAMBOLL.RAMBOLL-GROUP.GLOBAL.NETWORK security = ADS template homedir = /home/%D/%U template shell = /bin/bash winbind refresh tickets = yes mangled names = no usershare max shares = 100 Where to start looking? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 19

[opensuse] OpenBoard 1.3.4 now available as package
by Thorsten Bro 03 Mar '17

03 Mar '17

Hi Josep, it took a while, but due to me using the OpenBoard-Software in my HackWeek-Project, i pushed this topic a bit and got help from our packaging and Qt experts - so thanks to adamm, darix and danimo - we have now a well working OpenBoard package available in the Education project. My hackweek project: https://hackweek.suse.com/projects/geekoscreen-building-an-open-source-base… Try it out: https://build.opensuse.org/package/show?project=Education&package=OpenBoard https://software.opensuse.org/package/OpenBoard Cheers, Thorsten -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] the linux users guide to dismissing new technology
by nicholas 02 Mar '17

02 Mar '17

any change to technology is a threat to your existing knowledge and skills and should be rejected immediately. the more convoluted the existing technology is the better, it gives you and edge over others, which you need to defend (eg init). here is an incomplete list of potential stratergies: [1] divine truth: a useful prescript e.g. "a tool should do 1 thing and do it well" is a divine truth. it is not subject time, context, evidence, data or reasoning. [like the 10 commandments] (you can use divine truth to immediatly dismiss systemd irespective of technical arguments). [2] if the new technology doesnt work in the same way as the old, it is flawed. since the new tech requires new knowledge, it is obviously more complex QED. [be carefull not to apply this to windows vs linux] [3] dismiss any new features as pointless and unneeded. [4] faults: any shortcoming of new tech (be truth or hype) should be vocalised extensively. try to frame an argument such that the old tech has no problems. [5] avoid data, evidence, reasoning and context: rely on rumours, anecdotes, fud, comments on reddit, appeals to emotion and truthiness. [6] give the new tech whipping boy status: any problem for which a diagnosis does not exist should be attributed to the new tech. [7] condemn the new tech based on partial knowledge you havnt verified, and use this to form an apparently rational conclusion (e.g. systemd timer limitations) lets take an example: OP: "i had a problem, I dont know what it was, I used the wrong tools to diagnose it, ignored any recommendations on how to fix it, did something i didnt understand, and it still didnt work. whats more the same thing happened on all 5 systems which is statistically impossible if considered as independent (non correlated) failures" you now have all the hard evidence you need, and can let rip: [a] "the same thing happened to me - this is proof the system is rubbish" [b] "how could you ship a system that allows such a thing to occur" [c] "there is some fud on the internet from 5 years ago showing how bad the system is, whats wrong with you people" [d] "any tech that requires understanding is no good for home users" [ignoring the fact that the linux ecosystem itself fails under the premisses of the argument] -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] A hopefully stupid hardware question - power led?
by Greg Freemyer 02 Mar '17

02 Mar '17

All, I've got a PC that has power-on LED around the power button. I swear it used to be on when the PC was on and off when it was off. Now it seems the LED is almost always off (and maybe it is always off). Most of the time I don't care, but if I'm shutting down for some reason, I can't always tell when power down is done. Is there a bios setting to control that on some MBs? I just realized it could be the connector came loose. I don't recall when I last saw the light on. It's not something I look at most of the time, even though I sit 3 feet from it. fyi: AsRock X99 Extreme4 is my MB. Thanks Greg -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] Very basic dd question
by Stevens 01 Mar '17

01 Mar '17

I ask this kinda stupid question only because I really don't want to experiment with my only running computer. A friend has a bunch of very old Windows crap and wanted to know if I could "clone" a couple of his drives so he gave me 2 good drives and several "target" drives - all laptop ide, I think - anyway, I have one usb adapter that I can use, so the question is will the following work to clone a drive? dd if= /dev/sdb (the usb drive) of=/user/[my user home]/temp/bck If so, what would I need to tell it to make a bootable clone? Just reverse the commands? The drive is 540MB so space isn't an issue... And yes, disk partitioning software does see the usb drive and when it is plugged in the system allows me to open it in Dolphin. Thanks, Fred -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 19

[opensuse] Leap 42.2 - missing uucp package
by mh＠mike.franken.de 01 Mar '17

01 Mar '17

Hi *, is there any reason why Taylor uucp is no longer part of Leap 42.2, while Leap 42.1 contained it? I rely heavily on uucp, *because* it is an ancient protocol and nearly nobody (especially hackers) cares about it. Would be great, if someone could include it in Leap 42.2. TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] HP printer Leap 42.2
by michael norman 01 Mar '17

01 Mar '17

My HP D2300 usb printer has worked for many years. It is attached to one of my two pcs and shared between the two. This worked fine up to 13.2 but I cannot get 42.2 to share the printer. Sharing fails in Yast whereas it worked up to 13.2, when I try to sahre it using the CUPS interface I am not offered adminstrator settings (I always used my root password for this hitherto) so cannot change the settings to share the printer. All of this works on Linux Mint 18.1 fwiw. Is there a known fix for this ? M -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

9 35

[opensuse] Leap 42.2 - xf86-video-intel - plasmashell freezing on notifications
by mh＠mike.franken.de 28 Feb '17

28 Feb '17

Hi *, after a few months the problem still exists, even with the latest kernel, the latest X server and Mesa packages and the latest KDE Frameworks5 packages. So I dare to ask again: On one of my machines (Lenovo T420 notebook) I have a problem with plasmashell freezing often when a notification is shown. The notification frame shows up, but no content and then the complete desktop freezes. Killing and restarting plasmashell cures the problem for a short time - til one of the the next notifications wants to display something. It doesn't happen for all notifications, though. Using tools like notify-send the problem can not be reproduced, but notifications stemming from plasma-nm and plasma-workspace itself (like the one for a removed plasmoid) always lead to the freeze. The system originally was openSuSE Leap 42.2, but because of the problem I upgraded step by step to - the latest kernel from the kernel stable repo, - the latest X server plus everyting from the X11:Xorg repo - and the latest plasma workspace including everything from the KDE:Framework5 repo. The problem remained unchanged, though. A few more facts: - The X server is xf86-video-intel. - Switching to the modesetting driver doesn't help. - Switching off the compositor doesn't help either. - Everything worked with Leap 42.1 - No according entry in the journal or .xsession-errors* can be found. - Logging off or restarting the machine doesn't help in case the problems exists at that time. - *Switching off notifications completely cures the problem.* In found a few bug reports for plasma freezes, but none of them seems to fit exactly. Can I debug it and if so, how? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0