March 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Mounting windows-shares
by Koenraad Lelong 29 Mar '14

29 Mar '14

Hi, I'm migrating my laptop from Opensuse 12.2 to 13.1. One of the show-stoppers is mounting windows-shares. On 12.2 I use smb4k but on 13.1 smb4k is not working properly. So is there a way to gracefully mount windows-shares ? I know I can do this manually, on the command-line, as root. I also could add entries in fstab, but what happens when the server is not available, like at home ? I know I can browse the shares in Dolphin, but it seems not all applications can handle these "mounts", or do it in two stages like LibreOffice, with extra user/password entries and clicks. I googled a bit and I found autofs can do this also. I'm going to give that a try. Are there other options ? Thanks for your input. Koenraad. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] HEADS UP! for the adventurous
by Basil Chupin 29 Mar '14

29 Mar '14

Milestone 0 if openSUSE 13.2 is now available but be VERY careful if you decide to install it on a multi-boot system! Your mileage may vary of course but for me it was a disaster. I downloaded the KDE Live iso and (just for a change :-) ) it actually booted into Live mode. So I decided to be very brave and actually install it. I did this on a laptop which already has 13.1 installed but I had left space to be able to install at least 2 more OSs if I chose to. I chose to install 13.2 M0 in one of the empty partitions. The installation went fine until it came to the first "reboot your computer" which is when the wheels fell off :-( . The reboot saw that there were multiple systems installed and.....went braindead and decided that it couldn't boot into any and so the whole lot defaulted to the laptop's built-in boot procedure (which knows nothing). Now I cannot boot into my existing 13.1 and, of course, 13.2 is not visible to complete the installation. I am now working thru on how I can recover but I suspect that the only way for me at the moment is re-install 13.1 from scratch. BC -- A civilisation is judged by how it treats the most vulnerable. Lauren Smith - 30 January 2014 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 13

[opensuse] 13.1/GNOME: no more software update notifications
by Andrey Borzenkov 29 Mar '14

29 Mar '14

Since some time I noticed that I get no more popups about new updates in GNOME. I usually notice that people discuss some new updates and check with zypper and see bunch of them. I must admit I failed to understand what component actually checks for updates and displays notifications. /etc/sysconfig/packagekit-background did not change since initial installation (December) and problem appeared later. Unfortunately I cannot tell exactly when. So - what software is responsible for checking for and popping notifications about updates and does it have any log? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: SUSE-SU-2014:0459-1: important: Security update for Linux Kernel
by Linda Walsh 29 Mar '14

29 Mar '14

opensuse-security(a)opensuse.org wrote: > An update that solves 6 vulnerabilities and has 28 fixes is > now available. It includes one version update. > > Description: > > > The SUSE Linux Enterprise 11 Service Pack 3 kernel was > updated to fix various bugs and security issues. > > ------------------------------------------------------------ > ------------ WARNING: If you are running KVM with PCI > pass-through on a system with one of the following Intel > chipsets: 5500 (revision 0x13), 5520 (revision 0x13) or > X58 (revisions 0x12, 0x13, 0x22), please make sure to read > the following support document before installing this > update: > https://www.suse.com/support/kb/doc.php?id=7014344 > <https://www.suse.com/support/kb/doc.php?id=7014344> . You > will have to update your KVM setup to no longer make use > of PCI pass-through before rebooting to the updated > kernel. > ------------------------------------------------------------ The above doesn't seem to be a security update as a rare hw problem. The listed test on the linked page doesn't seem to work correctly. It doesn't echo that my system is 'affected', (even though it is). It seems the "-q" option is at fault. w/-q: # /sbin/lspci -nn | grep -qE '8086:(340[36].*rev 13|3405.*rev (12|13|22))' && echo "Interrupt remapping is broken" # w/o -q: # /sbin/lspci -nn | grep -E '8086:(340[36].*rev 13|3405.*rev (12|13|22))' && echo "Interrupt remapping is broken" 00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port [8086:3406] (rev 13) Interrupt remapping is broken looks like it has something to do with the pipefail section in bash, as this works: # grep -qE '8086:(340[36].*rev 13|3405.*rev (12|13|22))' < <(lspci -nn) && echo "Interrupt remapping is broken" Interrupt remapping is broken FWIW, having run this HW for 4+ years, I've never seen any of the warning messages that they indicate are symptoms of this problem, I did see the warning in the kernel about the problem and that my kernel was then marked tainted -- EVEN THOUGH, interrupt remapping had been turned off! ... Why implement a workaround that taints your kernel? I.e. isn't the workaround supposed to protect your kernel from becoming tainted? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] *many*: segfault ... error 7 in virtuouso-t
by Patrick Shanahan 28 Mar '14

28 Mar '14

openSUSE Tumbleweed kernel-desktop-3.13.6-20.1.g0509ce5.x86_64 intel i7 Vendor: "GenuineIntel" Model: 6.44.2 "Intel(R) Core(TM) i7 CPU 970 @ 3.20GHz" 32gb memory/no swap Mar 20 18:01:41 Crash kernel: [ 1830.124610] virtuoso-t[21071]: segfault at ffffffffffffffff ip 00000000007d5d6e sp 00007fe8ff833030 error 7 in virtuoso-t[400000+9aa000] Mar 20 18:01:45 Crash kernel: [ 1834.050473] virtuoso-t[21732]: segfault at ffffffffffffffff ip 00000000007d5d6e sp 00007f1b953a4030 error 7 in virtuoso-t[400000+9aa000] Mar 20 18:01:49 Crash kernel: [ 1837.904029] virtuoso-t[21849]: segfault at ffffffffffffffff ip 00000000007d5d6e sp 00007f414f81f030 error 7 in virtuoso-t[400000+9aa000] also happens in kernel-devel-3.13.6-19.4.g4727218.noarch and perhaps in kernel-devel-3.13.6-19.3.g4727218.noarch (cannot confirm here) nepomukctl restart stops it but only for ~10 minutes and resumes, volumously. bug report ?? against ?? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 5

[opensuse] switch from 32bit opensuse to 64bit
by Paul Neuwirth 28 Mar '14

28 Mar '14

Hallo, I accidently installed 32 bit opensuse on several machines. Is there an easy way to switch to 64bit? such as adding 86_64 repos and zypper --dup --allow-architecture-change (unfortunately this option doesn't exist)? Any hints? A notice in the setup, that a 32bit os is going to be installed on a 64bit system would be very nice... Thanks a lot in advance -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

14 41

[opensuse] Prevent system from grabbing USB bluetooth dongles?
by Stefan Gofferje 28 Mar '14

28 Mar '14

Hi, I'm trying to use US BT dongles in a virtual box but vbox can't attach them because the host won't release them. I'm not really familiar with hardware-stuff... How can I tell the host to not grab the BT USB dongles in the first place, so the vbox can grab them? -S -- (o_ Stefan Gofferje | SCLT, MCP, CCSA //\ Reg'd Linux User #247167 | VCP #2263 V_/_ Heckler & Koch - the original point and click interface

3 4

[opensuse] Advice needed re getting setting right for new monitor
by Basil Chupin 28 Mar '14

28 Mar '14

I just hooked up a new 27" LG monitor which has 2560x1440 resolution to my 13.1 system and using DVI-D cable. [#] Previously I was using a 24" monitor with 1920x1080 resolution which was connected using HDMI cable. The video card I am using in Nvidia Geforce 660 which can handle the 2560x1440 resolution. OK, I knew that I would have to make adjustments in 13.1 for this new monitor but: * when I boot the computer I do not see the GRUB menu; * it takes a loooong time to finally get the normal oS theme (which shows the gecko on the 'vine' tree on the RH of the screen; and * there is nothing else visible - normally you see the user name and the request to enter the logon password, but this is not visible; * on a hunch I typed in the password and got logged in. After I logged in I went to use the nVidia settings (Gecko>Applications>Applications>Nvidia X Server Settings) and while the settings recognised the monitor and its resolution I could not save the setting to /etc/X11/xorg.conf because I did "not have root" privileges. Trying to login as root fails because, as I stated above, the login menu is invisible. Also, running 'nvidia-xconfig' a root in a terminal when logged in as myself as the user does not seem to produce the necessary results in /etc/X11/xorg.conf because rebooting results in the same result as mentioned above: no Grub menu, blank screen except for the gecko on the green vine and therefore no logon menu. Can anyone suggest what I need to do to get 13.1 to boot normally - with the Grub2 menu et al? [#] The monitor is actually connected to the video card with both HDMI and DVI-D, but on the monitor the DVI-D is selected as the input. The nVidia settings in 13.1 Applications>Nvidia X Server Settings recognises both but has the DVI-D as the default connection (giving 2560x1440 resolution) while the unused HDMI connection shows 1920x1080 as the resolution - which is why I chose the DVI-D connector. BC -- Using openSUSE 13.1, KDE 4.12.3 & kernel 3.13.6-2 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

6 10

[opensuse] libvnc.so not loading - undefined symbol: _Z13getvnchomedirPPc
by Marco Schwarz 28 Mar '14

28 Mar '14

Hi, I have a problem with loading libvnc.so in 13.1, 32Bit with latest Patches. I enabled the loading of libvnc.so in /etc/X11/xorg.conf.d/10-libvnc.conf, and set the password. Now when I start X I get the following: [ 3.951] (II) LoadModule: "vnc" [ 3.952] (II) Loading /usr/lib/xorg/modules/extensions/libvnc.so [ 3.959] (EE) Failed to load /usr/lib/xorg/modules/extensions/libvnc.so: /usr/lib/xorg/modules/extensions/libvnc.so: undefined symbol: _Z13getvnchomedirPPc [ 3.959] (II) UnloadModule: "vnc" [ 3.959] (II) Unloading vnc [ 3.959] (EE) Failed to load module "vnc" (loader failed, 7) Anybody got a idea what could be wrong here ? Best regards, Marco -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

Re: [opensuse] Re: (offlist)Re: Post to opensuse@opensuse.org denied
by ianseeks 28 Mar '14

28 Mar '14

oops On Thursday 27 Mar 2014 12:43:53 Carlos E. R. wrote: > It did not go offlist ;-) > > > On Monday 24 Mar 2014 18:36:15 Linda Walsh wrote: > >> ianseeks wrote: > >>>> I don't have kmail currently configured, so I can not try to reproduce. > >>>> Others can try. > >>> > >>> i've logged a bug 332522 - lets see if anyone looks at it. > >> > >> --- > >> > >> Awesome!... Glad at least the didn't manage to convince > >> > >> us that it was the user's fault again... > >> > >> (that's what I usually get for doing anything they haven't > >> > >> tested...sigh) > > > > such is life in the open source world. i do feel bad when complaining > > about > > software faults when the the coding/testing has been done altruistically, > > oh to win the lottery and set up a KDEPIM coding team to fix and improve > > and help some of the coders that give their time for free and pay them. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0