May 2013 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Overloaded wireless?
by Greg Freemyer 03 Jun '13

03 Jun '13

All, At my parents house they have a old wireless router (maybe 7 or 8 years old). It normally works fine, but this weekend we had an extra 10 adults at their house and the wireless kept dropping from all the connected devices every minute or two. Then, this morning after everyone left, the wireless was stable again. The only thing I can think of is that there may be some kind of device limit on the router and when we exceeded the limit, it would kick off one connection in order to grant the next one and we ended up with a big game of king of the hill. Does that sound reasonable? To keep this on topic, one of the devices going on and off line was my opensuse 12.3 laptop. Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 10

[opensuse] Automatic deletion??
by John Bennett 02 Jun '13

02 Jun '13

Can somebody explain how this happened.... Camera plugged into 12.3 x64 PC via USB. Copied photos from: /var/run/media/john/NO NAME/DCIM/ to /home/data/_data/draw/camera/temp/, (2 dolphin windows open) waited for copy to complete, (checked with 'Notifications & Jobs'), and several minutes later, selected all files in /var/run/media/john/NO NAME/DCIM/ and deleted (no, didn't move to trash :-( ) and watched ALL (ie files in BOTH windows) get deleted.... Hard lesson learned (hope I didn't want any of those photos...). Can anyone explain? -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 8

[opensuse] Nepomuk - The Opposite Question
by John Andersen 01 Jun '13

01 Jun '13

I've searched high and low on Google, and can find tons of pages about how to kill off nepomuk. But, I actually want to make it WORK. (I know, crazy, right?) I have a mountain of code that I want to wade thru, and having something that would help me find all references to specific data names, or subroutines throughout the code base would be great. So its running on the machine, it indexed a boatload of stuff, I selected the directory structures I wanted indexed, and let it do its thing. The Places portion of Dolphin shows me a list of types, one of which is Documents and all the source code modules show up in there. But I STILL can't find file names or variable names (data elements) in this source code. At least it won't find any such thing in Dolphin's built in Search. Is there a some other tool I need to use for this? -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Please help understanding use of chmod and chown to get Wordpress installed
by Ted Byers 31 May '13

31 May '13

I asked about this on a Wordpress group, but they said this is a Linux question rather than a WordPress question. That I must ask reflects only that when it comes to administering a Linux box, I am a complete novice, even though I have been programming for decades. On the following page (http://codex.wordpress.org/Updating_WordPress), I find the following: "Automatic Update "Current versions of WordPress (2.7+) feature an Automatic Update. You can launch the automatic Update by clicking the link in the new version banner (if it's there) or by going to the Tools -> Upgrade (or Update for version 3) menu. Once you are on the "Update WordPress" page, click the button "Update Automatically" to start the process off. You shouldn't need to do anything else and, once it's finished, you will be up-to-date. "For Automatic Update to work, at least two criteria must be satisfied: "(a) file ownership: all of your WordPress files must be owned by the user under which your web server executes. In other words, the owner of your WordPress files must match the user under which your web server executes. The web server user (named "apache", "web", "www", "nobody", or some such) is not necessarily the owner of your WordPress files. Typically, WordPress files are owned by the ftp user which uploaded the original files. If there is no match between the owner of your WordPress files and the user under which your web server executes, you will receive a dialog box asking for "connection information", and you will find that no matter what you enter in that dialog box, you won't be able to update automatically. "(b) file permissions: all of your WordPress files must be either owner writable by, or group writable by, the user under which your Apache server executes. "On shared hosts, WordPress files should specifically NOT be owned by the web server. If more then one user owns different files in the install (because of edits made by deleting and re-uploading of files via different accounts, for example), the file permissions need to be group writable (for example, 775 and 664 rather then the default 755 and 644). File permissions (in general) should be adjusted as appropriate for the server environment (the shared host RackSpace CloudSites for example recommends 700 and 600 for a single ftp user, or 770 and 660 for multiple ftp users). See the file permission section for more (some files and folders require stricter permissions). " However, On the following page (http://codex.wordpress.org/Hardening_WordPress), I see: "Some neat features of WordPress come from allowing various files to be writable by the web server. However, allowing write access to your files is potentially dangerous, particularly in a shared hosting environment. "It is best to lock down your file permissions as much as possible and to loosen those restrictions on the occasions that you need to allow write access, or to create specific folders with less restrictions for the purpose of doing things like uploading files. "Here is one possible permission scheme. "All files should be owned by your user account, and should be writable by you. Any file that needs write access from WordPress should be writable by the web server, if your hosting set up requires it, that may mean those files need to be group-owned by the user account used by the web server process. "/ The root WordPress directory: all files should be writable only by your user account, except .htaccess if you want WordPress to automatically generate rewrite rules for you. /wp-admin/ The WordPress administration area: all files should be writable only by your user account. /wp-includes/ The bulk of WordPress application logic: all files should be writable only by your user account. /wp-content/ User-supplied content: intended to be writable by your user account and the web server process. "Within /wp-content/ you will find: "/wp-content/themes/ Theme files. If you want to use the built-in theme editor, all files need to be writable by the web server process. If you do not want to use the built-in theme editor, all files can be writable only by your user account. /wp-content/plugins/ Plugin files: all files should be writable only by your user account. "Other directories that may be present with /wp-content/ should be documented by whichever plugin or theme requires them. Permissions may vary. "Changing file permissions "If you have shell access to your server, you can change file permissions recursively with the following command: "For Directories: "find /path/to/your/wordpress/install/ -type d -exec chmod 755 {} \; "For Files: f"ind /path/to/your/wordpress/install/ -type f -exec chmod 644 {} \; What I do not understand is how to reconcile the ownership and mermissions required for automated updates with what is best to make the site as hard as is practicable. Note, this is for a multidomain install, but I own the hardware, so I do not know if this counts as a shared host or not. Note, I have not yet installed Wordpress on the machine in qustion, although I have downloaded and unpacked the latest release (so I can begin editing the configuration file as I need to do). As I did so using my account, I guess that means my account is deemed by the SOS to be the owner, and I do not know if I need to change ownership of some or all of the files once I move them all to document root (as the Wordpress installation instructions tell me to do), or if I need to do something else (I do not have a budget to let me hire a system administrator to do this for me, and indeed, in a business environment, I'd be relying on the MIS to handle all of this sort of thing). Can someone explain to me how one reconciles the ownership and permissions requirements for updates with those for ensuring system security, and what series of commands I should enter to put that into effect (relating that to the documentation of chown and chmod, would help me understand the how of it, if you don't mind).? Thanks Ted -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

Re: [opensuse] K3b doesn't recognize disc
by Mark Misulich 31 May '13

31 May '13

On 5/31/2013 12:07 AM, Mark Misulich wrote: > In Settings - k3b> Devices, only device /dev/sr1 is present. There is a > sentence present in the header that says "K3b tries to detect all your > devices properly. If K3b is unable to detect your drive, you need to > modify their permissions to give K3b write access to all devices." Well, we've gotten to the root of the problem it would seem. Perhaps the Developer for K3B could send some pointers your way. I suppose you (root) could look at the device in /dev and compare the permissions on /dev/sr1 and set /dev/sr0 to be the same but I seem to remember there is some function in OpenSuse that resets these on each boot. At least you could look there to see if they have different permissions. (these zero size entries in a "pertend" file system) But if you do decide to modify them, remember their settings. And perhaps seek better advice than I am able to give on the subject of permissions on /dev devices. Just throwing this out there... My K3B is installed from Packman, I had to allow vendor changes to get that to work, but it gets around some intentional breakage in the OpenSuse Packages. The package on my computer is installed from the packman repo, but it is the one that is malfunctioning. I opened a bug, here is the url for the bug: https://bugzilla.novell.com/show_bug.cgi?id=822648 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] Playing with Grub and Plymouth splash
by Marco Calistri 31 May '13

31 May '13

Hello openSuSErs! I have started to play with boot-splash (Grub2 and Plymouth) in order to change default boot-splash of openSuSE 12.3. I am still a bit confused about the requirements and settings and the way to update the boot loader. For example I have installed Plymouth theme Solar and I ran the "set-default-theme" and the "rebuild-initrd" script, now I see that during boot splash (after Grub2 splash) there is just a green progression bar in the bottom without any images on desktop, while at shutdown, I see a Sun with solar explosions animations in the low right corner of the screen and a centralized image (I don't remember the name reported now). Is this expected? What about DRM requirements? Is that a possible reason of the fact I don't see any images during boot and see only at shutdown? About Grub2 I have installed a boot spash from Cristian Rodriguez "SuSE Eleganter Bootsplash" (despite I ignore if it was compatible with 12.3). But at boot I keep seeing same Grub2 default openSUSE loader. About Grub2 conf ,I am in doubt about kernel parameters I have to add and/ or remove: my default kernel parameters line was "splah=silent" which I replaced with "quiet splash" as reported onto another Grub2 guide. Is there some good URL treating about Plymouth and Grub2 boot splash settings for openSUSE? Many Thanks! Cheers -- Marco Calistri (amdturion) opensuse 12.3 (Dartmouth) 64 bit - Kernel 3.7.10-1.4-desktop Gnome 3.6.2 Intel® Core™ i5-2410M CPU @ 2.30GHz × 4 - Intel® Sandybridge Mobile -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] NetworkManager and default route
by Alvin Beach 31 May '13

31 May '13

Hello all, Is there a way to set the interface to be the default route in NetworkManager? My desktop (openSUSE 12.3 KDE 4.10.3) has two interfaces: (1) Wifi USB dongle which connects to my router (Internet/Intranet) and (2) Wired Ethernet port that connects to my NAS[1]. In this situation, the Wired Ethernet interface because the default route. I want/need the Wifi interface to be the default route. Both interfaces work (connect, tx, rx). However, I need to reset the default route using /sbin/route command. I cannot seem to find the setting in the NM widget in KDE. Cheers, Alvin [1] Ideally, I would connect the NAS (DLink) to the router instead. However, the USB dongle sucks and drops the connection due to poor hardware. This messes up transferring large/many files (e.g. Digikam) from the NAS over wifi. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] For YaST fans
by Greg Freemyer 31 May '13

31 May '13

fasten your seat belts and read: http://opensuse.markmail.org/thread/wc5broxzcjuu7pl7 Greg -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] OS 12.1: Program crash (hugin) after last update
by Peter Suetterlin 31 May '13

31 May '13

Hello list, yesterday I did a 'zypper ref ; zypper up' on my openSUSE 12.1 computer (laptop). Amongst others, xorg-x11-server received an update to version 7.6_1.10.4-36.9.2 (yes, it's already a month old, but I don't 'up' too often) Today, I wanted to run hugin to do some panorama work, but all I got was The program 'hugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 1961 error_code 3 request_code 137 minor_code 4) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) [Inferior 1 (process 23357) exited with code 01] The hugin program I use is self compiled, so my first try was to recompile, but that didn't help - well, the 'serial' number has changed: (Details: serial 4118 error_code 3 request_code 137 minor_code 4) So I tried to revert to the previous version (7.6_1.10.4-36.5.1), but still get the same error. So it must be something else. But what? Has anyone seen similar problems after an update during this month, or an idea what to look for? Stuff that got updated was FreeCAD libphonon4 phonon-devel mkinitrd java-1_6_0-openjdk libtiff3 libcurl4 xorg-x11-server xorg-x11-Xvnc libcurl4-32bit libgnutls28 libtiff3-32bit libtalloc2 libwbclient0-32bit libtdb1-32bit libtdb1 libtalloc2-32bit libwbclient0 libtiff-devel libcurl-devel flash-player curl libgnutls-devel libtevent0 libsmbclient0 flash-player-kde4 libldb1 libgphoto2-6 rawtherapee darktable libgphoto2-6-lang photivo photivo-gimp libmpg123-0 mpg123 MPlayer gmplayer wxcam handbrake-cli xine-ui libopencv2_4 opencv opencv-devel plus a bunch of gambas3 packages But nothing (except the xserver) that seems connected to hugin. Pit -- Dr. Peter "Pit" Suetterlin http://www.astro.su.se/~pit Institute for Solar Physics Tel.: +34 922 405 590 (Spain) P.Suetterlin(a)royac.iac.es +46 8 5537 8507 (Sweden) Peter.Suetterlin(a)astro.su.se -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] What is it with this behaviour in 12.3?
by Basil Chupin 31 May '13

31 May '13

In another thread I mentioned that when I switch on my external 2TB USB WD HDD, Dolphin accesses it and displays its contents to me; but then when I go to use mc (Midnight Commander) this device is no longer mounted in /media as it has been in past many years but now is found in /var/run/media/<username>/<devicename> [in this case the volume name is WD]. Quite by accident a few minutes ago ('cause I am having another hassle, to be describe later) I discovered that the device is ALSO mounted in 'run/media/<username>/<device>'. (How many times is such a device 'mounted' and where else may I find it?) Has anyone else found this to be the case? BC -- Using openSUSE 12.3 x86_64 with KDE 4.10.1 & kernel 3.8.3-1 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

21 77