March 2016 - openSUSE Users - openSUSE Mailing Lists

[opensuse] sistemad-journal[359]: Forwarding to syslog missed 2 messages.
by Per Jessen 08 Mar '16

08 Mar '16

I know this should be fairly obvious, I guess the question is _why_ did syslog-ng miss some messages and do I do about it? On some 13.2 systems, I see this quite a lot, on e.g. 12.3 hardly ever. -- Per Jessen, Zürich (3.6°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 15

[opensuse] Can not delete BTRFS snapshot 1
by Vojtěch Zeisek 08 Mar '16

08 Mar '16

I have installed / with Btrfs. It works well. I'm just confused about one snapshot. I can normally delete snapshots created by zypper, manually or so on, but there remains snapshot 1 which I can't delete: # snapper list Type | # | Pre # | Date | User | Cleanup | Description | Userdata single | 0 | | | root | | current | single | 1 | | Mon Dec 21 14:08:36 2015 | root | | first root filesystem | # snapper delete 1 Deleting snapshot failed. # dmesg | grep BTRFS | tail BTRFS error (device sdc2): deleting default subvolume 259 is not allowed # btrfs filesystem show Label: 'system' uuid: b52578d1-f6c2-44b3-a0e3-af19016fb036 Total devices 1 FS bytes used 26.36GiB devid 1 size 439.00GiB used 29.07GiB path /dev/sdc2 btrfs-progs v4.1.2+2015100 System if Leap 42.1 (newly installed, no upgrade). Is this bug or feature? I thought I can delete any snapshot except 0. V. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/

2 3

RE: [opensuse] MS Designer Bluetooth keyboard (Bluetooth 4.0) not connecting to Dell Latitude E5550 using openSUSE Leap
by stakanov＠freenet.de 08 Mar '16

08 Mar '16

> -----Ursprüngliche Nachricht----- > Von: Tom Kacvinsky > Gesendet: Di. 08.03.2016 15:09 > An: opensuse(a)opensuse.org , > Betreff: [opensuse] MS Designer Bluetooth keyboard (Bluetooth 4.0) not connecting to Dell Latitude E5550 using openSUSE Leap > > > > -----Ursprüngliche Nachricht Ende----- At the time I did post this on the mailinglist and had quite some "pun" about Bluetooth not being broken on leap. Factually it is. Your problem will be as follows: the BT mouse/keyboard whatever will pair correctly, after system suspend or after reboot/login/out it will try to connect/pair but will not succeed in doing so. Try to pull the BT dongle and to put it back in (if you use any). That should allow the correct loading of the module. At the time I did not report the bug, because I was quite vocally "corrected" that this was "well known issue". If you open a bug report please tell the number here, I will then list my experiences too. I think at this point a report might be indicated. P.S. this will hit everything but 2.1 Protocol version of BT AFAIK --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] MS Designer Bluetooth keyboard (Bluetooth 4.0) not connecting to Dell Latitude E5550 using openSUSE Leap
by Tom Kacvinsky 08 Mar '16

08 Mar '16

Hi, Using the hardware listed above, I am able to pair my keyboard, but not connect. I am willing to provide debug info, I am just not sure what I should provide. I am using the KDE interface to setting up Bluetooth devices. This works just fine for the Designer Mouse that came wit the board. The difference between the two is that the keyboard requires a PIN for pairing and the noise doesn’t, so I am thinking this might have something to do with auth/trust. Then again, this might be a known issue. I did not see anything on the openSUSE bug tracking page. If any one has any input, I’d appreciate hearing it. Thanks, Tom N��r��y隊Z)z{.�ﮞ˛��m�)z{.��+�:�{Zr�az�'z��j)h��Ǿ� ޮ�^�ˬz��

1 0

Re: [opensuse] Cannot Login to new system
by Terrance Eck 08 Mar '16

08 Mar '16

On 3/7/2016 2:33 PM, John Andersen wrote: > On 03/07/2016 10:12 AM, Terrance Eck wrote: >> I installed the 64bit Leap 42.1 and when it rebooted and presented the login screen my password >> failed. I was >> able to get into the terminal mode (ALT-F1) and I could login as user and root. > Ok, so those two sentences contradict each other. > > Your password didn't fail if you were able to log in at a terminal. > > It may be that the X server refused to start, which may be due to a > proprietary video driver. (Most likely the case if its Nvidia). > > > --- > Unless you change settings, I don't think leap will let you log in as root > in graphics mode. > It is not really a contradiction. The password is valid under the basic Linux system but does not let me login to the graphical mode. So can anyone help provide a solution. The video card is Nvidia. Whatever video driver is being use would have be from the opensuse dvd. I don't know how it could be using a proprietary driver. Thanks -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

[opensuse] curious warning message "wihite on black background" of Plasma
by stakanov＠freenet.de 08 Mar '16

08 Mar '16

I had a full screen warning, white writing on black background. It went: Your screen saver has been damaged. Please press CTL+F2 and enter (now I do not remember exactly but it was: screenctl unblock or something similar). I noticed that unlike normally when CTL+F1 is free, this was taken by some system funktion and only CTL+F2 was available. It was for me more convenient to reboot the system (to be sure that nothing is "zombying" around). Did anybody else see such a warning? Seems to be related with the recent crashes of plasma when using the "change user" function. Is there a logfile to eventually gather information should this happen (could be useful for a bug already opened on the issue). Thank you. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! https://email.freenet.de/mail/Uebersicht?epid=e9900000451 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

RE: [opensuse] Cannot Login to new system
by stakanov＠freenet.de 08 Mar '16

08 Mar '16

> -----Ursprüngliche Nachricht----- > Von: Terrance Eck > Gesendet: Mo. 07.03.2016 19:12 > An: opensuse(a)opensuse.org > Betreff: [opensuse] Cannot Login to new system > > I installed the 64bit Leap 42.1 and when it rebooted and presented the > login screen my password failed. I was > able to get into the terminal mode (ALT-F1) and I could login as user > and root. How can this problem be solved? > > Thanks > It would be good to get back using Linux > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > > > -----Ursprüngliche Nachricht Ende----- So just to be a bit more sure: this is a fresh install of leap on a PC or a Laptop? What does mean "my password fails". That means you login and it gets all black screen with only the cursor or you stay at the login of sddm? Did you install with "update during installation" or did you just install from DVD and wanted to update later? In case you did not update yet. Login in tty1 and su - then do zypper ref then zypper dup (provided that up to now you have only the default repos activated and provided you have a working internet connection. Once done, try to restart the whole machine and to login. Ah, i forgott, there may be a keyboard layout problem. When loging in to sddm, did you check at the left in the upper screen that the right keyboard layout is supported? If your password has y and z inside try to invert them while login in, maybe it is just this little. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 7

[opensuse] usbip ?
by Greg Freemyer 08 Mar '16

08 Mar '16

All, Has anyone setup a USB server via usbip? Apparently usbip is a default feature of recent Linux kernels. I know little about it. My use case is I have 4 license dongles that allow commercial software to run. Currently I have to physically move it from one computer to another to run the licensed software. I would like to setup a dongle server that had all the license dongles permanently connected, then use usbip to export them out to the client machines. I'd be fine with exclusive access, meaning only one client at a time could run the licensed software, but I would really like the flexibility of not having to physically move the dongles around. The client PCs are are running Windows, but it seems the server could be running openSUSE. I already have a PC designated to be designated for this task. Any insights? Thanks Greg -- Greg Freemyer www.IntelligentAvatar.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

RE: Re: [opensuse] Cannot Login to new system
by stakanov＠freenet.de 08 Mar '16

08 Mar '16

Just to be sure. You are using nouveau driver. This could be the problem. Could you try to login into safe mode setting during the boot up? There is he second line of grub telling you to pass special parameter. Could you set up there the paramenter "nomodeset" to grub when starting up? Where nomodeset is the parameter and has to be written without the gimmicks. Try to log in then. You can also try to change password via yast. You can reach yast any time in the command line version (as you can login as yourself and su - then write yast. You will find yourself in a old but nice texmode interface. To navigate you use the tab and the enter key. You can create a new user with an easy password (user test, password test). Say yes to the questions (as you will delete that user at the end if all works. Then login into test with the new account. Does this work as expected? As for your question: yes everything works from the tty 1 interface (Fn + F1) If you want to try, with the yast interface you can also join the nvidia repo with the proprietary driver if you still to not manage to login. Then you select the appropriate driver for your graphic card, install and exit yast. Reboot and you are done. That I would try it as last step. Let me know if you need advice and if you have problems. P.S. it comes to my mind that graphical login will fail if for some reason you are out of space or in the root directory (if you did choose it too small) or if you selected a separate /home and you are out of space in that home directory. In both cases login will jump back to the sddm. you can check as root with df -h this will give you the free space on the partitions you have. None of the "use%" values are allowed to be 100%. You may post here if you have doubts. --- Mail & Cloud Made in Germany mit 3 GB Speicher! https://email.freenet.de/mail/Uebersicht?epid=e9900000450 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Re: backporting OBS build of Base:System(systemd v = 228) to Leap; builds, but rpm install returns "Problem: nothing provides this-is-only-for-build-envs needed by systemd" ?
by PGNet Dev 07 Mar '16

07 Mar '16

> Leap's systemd is at v = systemd-210-86.1.x86_64. Since it's now clear from systemd-maintainers that there's no interest in upgrading Leap release, cc:'ing here to get some insight on getting @OBS builds working & installable ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2