January 2015 - openSUSE Users - openSUSE Mailing Lists

[opensuse] latest gnumeric update segfaults
by Carl Hartung 30 Jan '15

30 Jan '15

Hi All, Just an FYI re OpenSUSE 13.2 x86 64-bit KDE 4.14.3 I just had to roll back gnumeric (& gnumeric-lang) to the prior version due to the latest updates making it unstable / unusable. Anyone else see this? TIA & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] KDE does not launch on login when connected with VNC
by Paxton Scott 29 Jan '15

29 Jan '15

Joe, Thanks for your kind suggestions. I do not see how doing the steps you suggest addresses the KDE failure to start from the KDM login prompt. Normally, my VNC server is started by xinetd on port 5901. I can change that to 5900 and connect, but at this point I can not tell what display number it uses. Behavior is the same. But, I assume that you are expecting me to work on the local machine using the virtual consoles. Never done any of that. What information is it that you are expecting me to find performing the 5 steps you listed? I am thinking no one has gotten a login to a DE to work over VNC on 13.2. Looks my best solution is to use 12.2 which I use daily. Paxton On Wed, Jan 28, 2015 at 6:01 PM, Joe Zappa <joe.3appa(a)gmail.com> wrote: > Paxton Scott wrote: >> >> Greetings! >> I am new to the mail list, so I apologize for any fopahs :-) >> >> Although there are several 'how to's" regarding VNC on openSUSE 13.2 I >> have not found anyone who has actually been successful in creating a >> one time session that logs into any desktop. >> >> What I want to do is use VNC to connect to my opensuse 13.2 machine, >> get the login page, login and get the KDE desktop. >> >> (I do this successfully with opensuse 12.2, it works great.) >> >> My VNC connects just fine, asks for my password and then presents me >> with the login screen. >> If my username/password is incorrect, it reflects that. >> When I enter the correct username and password, the login dialog >> disappears but nothing happens, just the normal green background. >> Three or maybe it is 4 minutes later, the login dialog reappears. >> Something times out I suppose. >> >> Everything works normally locally. >> >> In the system message file I find these two lines essentially at the same >> time: >> ...kdm: localhost:1[1094]: pam_unix(xdm:session): session opened for >> user paxton by (uid=0) >> ...kdm: localhost:1[1094]: pam_unix(xdm:session): session closed for >> user paxton >> >> >> Since VNC connects and seems stable, and KDE works fine locally, I >> figure there is some issue with launching KDE while connected with >> VNC, but I do not know where to look to fix this. >> >> I have not modified my xstartup file. >> >> Hope someone can give me some guidance > > > > Yes. > > The easiest way to start your debugging problem is to > > 1. start your VNC server to serve out DISPLAY :0 (virtual console ALT-F7). > 2. start a KDE session on the usual virtual screen (ALT-F7) (DISPLAY :0) > 3. start a second login on ALT-F8 and login (DISPLAY :1) > 4. logout of the session on ALT-F7 > 5. Start up a VNC viewer on ALT-F8, and attempt to connect to a server on > localhost > >> >> Have fun, >> Paxton >> > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Libreoffice issue
by ianseeks 29 Jan '15

29 Jan '15

Hi Is there an opensuse list for discussing Libreoffice? I can't find a specific one. i'm getting a regular issue with opening a writer document, copying some text (highlight with mouse and ctrl-c) and when i'm about to do something with the copied text, the keyboard locks up (num light on) and the mouse can move about the screen but cannot click on anything. I have to reboot the system to recover. I will report this as a bug but i can't reproduce it at will. regards ian -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 4

[opensuse] KDE does not launch on login when connected with VNC
by Paxton Scott 28 Jan '15

28 Jan '15

Greetings! I am new to the mail list, so I apologize for any fopahs :-) Although there are several 'how to's" regarding VNC on openSUSE 13.2 I have not found anyone who has actually been successful in creating a one time session that logs into any desktop. What I want to do is use VNC to connect to my opensuse 13.2 machine, get the login page, login and get the KDE desktop. (I do this successfully with opensuse 12.2, it works great.) My VNC connects just fine, asks for my password and then presents me with the login screen. If my username/password is incorrect, it reflects that. When I enter the correct username and password, the login dialog disappears but nothing happens, just the normal green background. Three or maybe it is 4 minutes later, the login dialog reappears. Something times out I suppose. Everything works normally locally. In the system message file I find these two lines essentially at the same time: ...kdm: localhost:1[1094]: pam_unix(xdm:session): session opened for user paxton by (uid=0) ...kdm: localhost:1[1094]: pam_unix(xdm:session): session closed for user paxton Since VNC connects and seems stable, and KDE works fine locally, I figure there is some issue with launching KDE while connected with VNC, but I do not know where to look to fix this. I have not modified my xstartup file. Hope someone can give me some guidance Have fun, Paxton -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] wicked/dhcp fails when network isn't connected ?
by Per Jessen 28 Jan '15

28 Jan '15

I'm not sure, so before I open a report, does anyone recognize this scenario: A system has an interface (eth0) configured with dhcp. The system is rebooted, but eth0 is not connected to anything. Obviously any dhcp requests will fail until the cable is plugged in. However, when I plug in the cable, the interface does not acquire an address. I have to manually if-down/up it. -- Per Jessen, Zürich (3.9°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 8

[opensuse] Firefox 34.0.5
by Basil Chupin 28 Jan '15

28 Jan '15

What is it with this version of Firefox 34.0.5?! It decides at random times to SHUTDOWN and RESTART - all by itself! I have seen this happen when I am viewing a TV channel (using VLC) and FF then "overwrites" what I am watching. At first I thought that this had something to do with some relationship between VLC and Firefox v 34.0.5 but this is not the case: Firefox just simply restarts even though I am doing something else! This has NEVER happened with previous versions of Firefox. So, why is 34.0.5 so "special" (and such a PITA)? BTW, this restart by FF occurred a few minutes ago while I am using *Tumbleweed* (contrary to what you read below in my Signature line) and it also has occurred in 13.1 and 13.2 - hence this post. Something to do with the AddOns I am using, you say? Hardly think so as I have been using the same AddOns for years and FF has never behaved as it does now. Anybody else having similar experience, or know of why this is occurring? As I said this is a random occurrence (although at one time I thought I noticed that it occurs ~120 minutes after I start viewing a TV channel). BC -- Using openSUSE 13.1, KDE 4.14.3 & kernel 3.18.1-1 on a system with- AMD FX 8-core 3.6/4.2GHz processor 16GB PC14900/1866MHz Quad Channel RAM Gigabyte AMD3+ m/board; Gigabyte nVidia GTX660 GPU -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 21

[opensuse] degraded RAID1 question
by Istvan Gabor 27 Jan '15

27 Jan '15

Hello: I have several RAID1 mirror devices. For some reason, I don't know why, some of them have been degraded. For example, originally /dev/sdb8 and /dev/sdc8 formed md8 (/dev/md8). This was mounted as /dev/disk/by-id/md-name-pc:8 to /mnt/disk8. Now the above array is degraded, more precisely forms two degraded arrays. One is md8, according to /proc/mdstat: md8 : active raid1 sdc8[0] 31455164 blocks super 1.0 [2/1] [U_] The other is: md121 : active raid1 sdb8[2] 31455164 blocks super 1.0 [2/1] [_U] That is one device from the original array has become part of another array, md121, which hasn't been defined before. Investigating the two arrays separately it seems that both has data which is not on the other 'array'; it seems that the two arrays were used alternatively in the last few days. I can mount them separately and synchronize the data on them manually, but I wonder if there is a better, automatic approach. I also would like to set back the original scenario, where both devices are part of md8. I don't know where the md121 name comes from, and how I can change it back to md8. My /etc/mdadm.conf doesn't have device md121, it has only md8. ARRAY /dev/md/pc:8 UUID=44.... mdadm --detail --scan gives: ARRAY /dev/md/pc:8 metadata=1.0 name=pc:8 UUID=44.... ARRAY /dev/md/pc:8 metadata=1.0 name=pc:8 UUID=44.... The two UUIDs are the same. Any idea to fix this? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] broadcom wireless
by Hans Krueger 27 Jan '15

27 Jan '15

I'm looking for a broadcom wireless expert for help I'm having trouble with my wireless card now it worked fine when I first installed Linux 3.11.10-25-desktop openSUSE 13.1 (Bottle) (x86_64)13.1 kde Version 4.12.3 a few updates back it started acting up trying to fined the problem now it just quits working for no reason and randomly it's a dell E6400 latitude with Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01) card tried to start and stop it from the command line the only way is to reboot the machine I get this in the logs when this happens device state change: unavailable -> disconnected (reason ...30 42] 015-01-25T17:24:27.809728-05:00 dellaptop kernel: [120859.001570] ERROR @wl_cfg80211_scan : WLC_SCAN error (-22) any help would be appreciated -- Hans Krueger hanskrueger007(a)roadrunner.com registered Linux user 289023 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: [opensuse-factory] NetworkManager-1.0 soon to be ready for testing
by James Knott 27 Jan '15

27 Jan '15

On 01/27/2015 01:16 PM, Jan Engelhardt wrote: > On Tuesday 2015-01-27 18:50, Shawn W Dunn wrote: >> > >> >Some of the new Features/Bugs/Changes [of Networkmanager] include: >> > >> > + A faster, lighter-weight (though less capable) internal DHCP >> > client has been added > I find it strange that everybody is suddenly writing their own > DHCP clients. > First networkd, now networkmanager. What's wrong with dhcpcd? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] disabling KDE wallet, openSUSE 13.2 with default KDE4
by Istvan Gabor 27 Jan '15

27 Jan '15

Hello: This is in openSUSE 13.2 with its default KDE4 (4.14.3). I am trying to disable KDE Wallet in Configure Desktop -> Common Appearance and Behavior -> Account Details -> KDE Wallet: I uncheck the "Enable the KDE wallet subsystem" checkbox. Then I click "Apply". The " Apply" button grays out. Then I go to the next config option or close the window. A message window appears titled "Apply Settings - System Settings" and saying "The settings of the current module have changed. Do you want to apply the changes or discard them?" I click "Apply". Another window titled "KDE Wallet Control Module - System Settings" appears saying: "Sorry, the system security policy didn't allow you to save the changes." I click OK. I go back to KDE Wallet settings: KDE Wallet tickbox is still on, KDE wallet hasn't been disabled. This is in a VNC session if it matters. How can I disable KDE Wallet? I don't want to configure it. Even better to get rid of this stuff competely? Thanks, Istvan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10