March 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] apper with 12.3
by Greg Freemyer 20 Mar '13

20 Mar '13

Just a note that apper with 12.3 seems much better behaved. I've left it installed and have used it a few times to pull down updates in the last couple weeks. In 12.2 and before, I would have got mad at it by now and removed it. People that haven't used it in a while may want to give it a chance again. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: [smartmontools-support] WARNING: smartmon-tools 6.1 locks Areca-SAS driven system
by Hans-Peter Jansen 20 Mar '13

20 Mar '13

Dear Alex, On Mittwoch, 20. März 2013 11:38:49 Alex Samorukov wrote: > On 03/19/2013 06:51 PM, Hans-Peter Jansen wrote: > > Dear Stanislav, dear smartmontools developers, > > > > I've upgraded one of my servers to smartmontools 6.1 today, that happens > > to > > drive a Areca SAS controller, specifically: > > > > <5>[ 7.206669] Areca RAID Controller6: F/W V1.46 2009-01-06 & Model > > ARC-1680 <6>[ 7.270516] scsi6 : Areca SAS Host Adapter RAID > > Controller( RAID6 capable) <6>[ 7.270516] Driver Version 1.20.00.15 > > 2010/08/05 > > > > Thing is, the system freezes immediately after running (updating) smartd. > > rpm stopped at 89%, and the system was *locked*. While I can switch > > consoles, even Sys-Req S and U doesn't finish anymore, while B worked. > > :-( > > Sounds scary. Please do some tests: > > 1) Test on smartd from fresh svn to make sure that local patches are not > affecting the result. > 2) Test if smartctl --scan and --scan-open commands works. > 3) try to run it with smartd -d -r ioctl and provide resulted output. Will do that soon (hopefully I can do these tests in single user mode). > Also i would recommend to make sure that RAID firmware is up to date, > because this could be caused by wrong firmware. Honestly, I don't buy this argument. This behavior points to a serious *kernel* problem in this area, since a system app, even running as root, should never ever be able to firmly lock the system, no matter what firmware version it is running. But such issues must be analysed and fixed, of course.. This mail was intended to both: warn users about it, and harvest some hints on how to preceed. Thanks for sharing the tests, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Duplicate NFS mounts in Places
by Alvin 20 Mar '13

20 Mar '13

Hello all, I upgraded from openSUSE 12.1 to openSUSE 12.3. Both were running KDE 4.10. I have noticed that some of my NFS mounts are duplicated in the "Places" panel in Dolphin (left-hand side). The duplicated items have an additional '/' in the name (e.g. //docs). My NFS server is openSUSE 12.2. I am using NFS4. My fstab entry is: server:/docs /mnt/server_docs nfs4 default,intr,hard,user 0 0 When I select the entry that has a single '/' I get a notification that: "Could not mount the following device: /docs on server." and the text in the red bar in Dolphin states: "An error occurred while accessing '/docs on server', the system responded: mount.nfs4: /mnt/server_docs is busy or already mounted" If I select the entry with two forward slashes ('//'), it works just fine. I suspect this is an issue caused by the upgrade (e.g. mixed up config file?). Does anyone know of a way to force Dolphin or KDE to refresh its listings? Thanks, Alvin -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] kwin and minimized windows
by Roger Oberholtzer 20 Mar '13

20 Mar '13

On an openSUSE 12.1 system, a user has accidentally set an app's window property so that it is always minimized. They claim that they cannot get to the window decoration part that lets them change this, as they could before it became permanently minimized. I see that the settings that control this are in: $HOME/.kde/share/config/kwinrulesrc Is there a GUI to change this? Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer(a)ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Live upgrade with jump?
by Claudio ML 20 Mar '13

20 Mar '13

Hello all, Just a simple question: Is officially supported the network upgrade with a jump from versions ? Like 11.4 ---> 12.3 or similar. Or is always better upgrade without jumps? 11.4 -> 12.1 -> 12.2 -> 12.3 .... Cordially, Claudio. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10

[opensuse] Re: Live USB and bulk install
by Malcolm 20 Mar '13

20 Mar '13

On Wed 20 Mar 2013 09:27:49 AM CDT, Anton Aylward wrote: >Malcolm said the following on 03/20/2013 09:01 AM: >> Hi >> And PXE boot them..... >> > >Client/manager says no. >These weren't thin 'client' machines to start with. > > Hi To do the install.....? if your using your laptop, set up the pxe server, connect a switch and hookup a few systems at a time to do the install then switch off the pxe boot (assuming the systems in question have the ability). -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.3 (x86_64) Kernel 3.7.10-1.1-desktop up 2 days 17:10, 5 users, load average: 0.02, 0.04, 0.11 CPU Intel® i5 CPU M520(a)2.40GHz | GPU Intel® Ironlake Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Re: Live USB and bulk install
by Malcolm 20 Mar '13

20 Mar '13

On Wed 20 Mar 2013 01:56:43 PM CDT, Per Jessen wrote: >Anton Aylward wrote: > >> In the past I've only ever had to install Linux on single machines at >> a time, but a new client has raised the question of doing a bulk >> install on many (more than 20, possibly as many as a hundred) >> workstations. Step and repeat, all the same. > >AutoYaST ? > >If that's too much effort for a one-off, and if the machines are all >the same, how about installing one and then cloning it? Just a >tar-copy will do. > > > Hi And PXE boot them..... -- Cheers Malcolm °¿° (Linux Counter #276890) openSUSE 12.3 (x86_64) Kernel 3.7.10-1.1-desktop up 2 days 16:30, 5 users, load average: 0.17, 0.13, 0.13 CPU Intel® i5 CPU M520(a)2.40GHz | GPU Intel® Ironlake Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] No text in Acroread - 12.3
by James Knott 20 Mar '13

20 Mar '13

I installed Acroread in openSuSE 12.3. There is a problem where boxes appear in place of text in the menus etc. The document appears fine. Any idea on the cause & fix? tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

Re: [opensuse] Upgrade to 12.3 caused akonadi problems/crash in 11.4
by Marc Chamberlin 20 Mar '13

20 Mar '13

On 3/18/2013 11:01 AM, Jan Ritzerfeld wrote: > Am Sonntag, 17. März 2013, 22:12:50 schrieb Marc Chamberlin: >> I have been running an openSuSE 11.4 system with a number of server >> applications such as Tomcat, James, Bacula etc., and decided it was time >> I upgrade it to 12.3. I have always followed a model of keeping /home in >> it's own partition and installing each new version of openSuSE into it's >> own partition. > I am doing the same. I updated to 12.3 this weekend. > >> In this way, my thinking was that I could keep running >> the older version of openSuSE until I get all the servers and >> configuration files (found in /etc /srv and elsewhere) upgraded and >> running under the newer version of openSuSE. That model has always >> worked in the past and I thought openSuSE developers would continue to >> adhere to that model as well... >> [...] > I am not a "openSUSE developer" but I always clearly stated, when being > asked or when I advised a KDE update, that you should not do that. You > should backup your old /home. You should never go back after KDE has updated > and migrated(!) its configuration and databases. If it worked for you in the > past, it was pure luck. > > Sorry > Jan Thanks Jan for replying. I guess that makes it even harder to do upgrades of openSuSE. I wish the openSuSE developers/designers, along with the Linux community in general, would give some more thought and directions on how we users are suppose to be able to migrate to newer releases of an OS while at the same time being able to regress back to previous releases when we have to. Having to maintain separate /home directories-partitions for each release would be a major PITA because of the divergences that will happen, and keeping data synchronized between them (can you say mail databases for example?) while running under different versions of openSuSE. Some of us poor users don't have the luxury of setting up separate servers and client computers when migrating from one OS to the next, and must do it in place. And getting a new system up and running takes time and we cannot afford to have our computers down during production/work hours, so the migration process can take a long time to complete. I know, I been through this process quite a few times now. I have a few tricks in place that help, for example I yank a lot of stuff out of /etc for different server configurations files and link them back in to versioned directories (in a separate partition which then retains configuration files for running the servers under different versions of openSuSE as well as different versions of the servers themselves.) Guess I will have to start doing something similar for the /home directories and figure out what stuff KDE/openSuSE is likely to touch and yank that stuff out to a separate partition with versioned directories as well. Either way it is a PITA and I wish there was a well defined (and adhered to) model for laying out partitions and directories so we can easily support regressing back when it is necessary to do so. Marc... -- "The Truth is out there" - Spooky -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] WARNING: smartmon-tools 6.1 locks Areca-SAS driven system
by Hans-Peter Jansen 19 Mar '13

19 Mar '13

Dear Stanislav, dear smartmontools developers, I've upgraded one of my servers to smartmontools 6.1 today, that happens to drive a Areca SAS controller, specifically: <5>[ 7.206669] Areca RAID Controller6: F/W V1.46 2009-01-06 & Model ARC-1680 <6>[ 7.270516] scsi6 : Areca SAS Host Adapter RAID Controller( RAID6 capable) <6>[ 7.270516] Driver Version 1.20.00.15 2010/08/05 Thing is, the system freezes immediately after running (updating) smartd. rpm stopped at 89%, and the system was *locked*. While I can switch consoles, even Sys-Req S and U doesn't finish anymore, while B worked. :-( Reverting to version 6.0 resolved it for me. I'm using the simplest of all cases of /etc/smartd.conf, since that worked reasonably well: DEVICESCAN -d removable -m root While userspace is rather old (openSUSE 11.1/i586), it's controlled by a reasonably current kernel: <5>[ 0.000000] Linux version 3.8.3-3-pae (geeko@buildhost) (gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) ) #1 SMP Fri Mar 15 08:16:33 UTC 2013 (1ca6928) All packages are built on OBS, smartmontools here: https://build.opensuse.org/package/show?package=smartmontools&project=home%… I would seriously consider reverting the 6.0 -> 6.1 transition in the openSUSE repos, until this issue is fixed. Let me know, what additional information I can provide in order to resolve the issue. Thanks, Pete -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 3