October 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] How to stop automatic mounting of USB drives
by Graham Smith 13 Oct '14

13 Oct '14

Hi, I wish to stop users from mounting USB drives without authorisation. System: openSUSE 13.1 KDE 4.14.1 I believe the settings are in the polkit files but unsure of the actual file or the structure of the commands required. -- Thanks, Graham Smith -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] UEFI dual boot
by Wolfgang Rosenauer 12 Oct '14

12 Oct '14

Hi, seems I'm still very new to UEFI and currenty way of bootloading. I've got a machine with UEFI (but w/o secure boot) which currently only has 13.1 installed. Now I've added 13.2rc1 to another partition. (During installation the bootloader refused to do anything with EFI because of an architecture conflict for x86-64; confusing but not that relevant here.) So I've got 13.1 and 13.2 both installed now but normal boot up shows only the 13.1 boot entry still. Now I've checked grub2 config on 13.1 which does not contain 13.2 (even after a grub2-mkconfig run the os prober didn't find 13.2). Then I checked the grub2 config on the 13.2 partition and in that I see two boot entries (one for 13.2 and one for 13.1). So all I would need to do is make UEFI load grub2 from the 13.2 partition I guess but I fail to understand how to do that. Is that defined via efibootmgr in that strange string? Boot0000* openSUSE HD(1,800,4e000,7e36557b-6396-4f70-9287-7d7b8e00c927)File(\EFI\opensuse\grubx64.efi) or is grubx64.efi just loading some magically marked partition like the boot flag in MBR? (I have GPT here obviously.) How to do that? Any input? Thanks, Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] how to correct scrambled subject lines
by Carl Spitzer 12 Oct '14

12 Oct '14

[opensuse-offtopic] =?UTF-8?B?UmU6IFtvcGVuc3VzZS1vZmZ0b3BpY10gUmU6IFtvcGVuc3VzZS1vZmY=? =?UTF-8?B?dG9waWNdIFJlOiBbb3BlbnN1c2Utb2ZmdG9waWNdIFJlOiBbb3BlbnN1c2Utb2Y=? =?UTF-8?B?ZnRvcGljXSBGd2Q6IFRoZSBDb21wbGV0ZSBIaXN0b3J5IG9mIE1vbnNhbnRvLCA=? =?UTF-8?B?4oCcVGhlIFdvcmxk4oCZcyBNb3N0IEV2aWwgQ29ycG9yYXRpb27igJ0=? They appear like normal subject lines in Evolution but not in the source. Thus frustrating filtering which is based upon the source of a message not interpretation. Is there a program for correcting this so filters can work?? CWSIV -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] ddrescue bottleneck on faulty drive
by Otto Rodusek 12 Oct '14

12 Oct '14

Hi ListMates, I'm not sure if this is the correct forum but hopefully someone will have an answer for me. I have a faulty 500Gb notebook disk that I want to clone and recover. I use ddrescue (with the -n option) to clone the faulty hdd to a new hdd. The problem is that based on the current stats, it will take days/weeks to complete the clone!!! I know that I have a faulty drive, I just want to clone the faulty drive unto a new drive, simply skip the faulty sectors (zero fill on the destination drive) and continue the clone - I don't want the system to keep retrying over and over to read the faulty sector - try once and die and set the destination sector zero-filled. Where there are no errors on the original drive the copy goes fast, but once it hits a bad sector it is painfully slow!!!! So where is the bottle neck? 1) ddrescue - according to the docs if one uses the -n option it wont bother to read or recover the faulty sectors on the faulty drive (I also tried -r1 - read/retry once) but to no avail. BTW I tried both read from beginning of disk as well as reading from back (-R), but alas to no avail as once it gets to the faulty sectors it becomes painfully slow. 2) is it a kernel parameter - ie how to turn of retrying to read the faulty sector n..times 3) is it a sata driver parameter - ie likewise how to turn of retrying to read the faulty sector n..times 4) or is it the firmware on the faulty hdd? (in that case I'm not sure there is a solution to turn of retrying faulty sectors or remapping them) I'm not sure there is a solution but if anyone knows any help would be most appreciated. Thanks in advance for any help. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

7 12

[opensuse] this I have received in browsing for open suse 13.2
by Hans Walter Finckh 12 Oct '14

12 Oct '14

XML Parsing Error: unexpected parser state Location: jar:file:///C:/Programme/Mozilla%20Firefox/browser/omni.ja!/chrome/browser/content/browser/aboutneterror/netError.xhtml Line Number 308, Column 50: <div id="ed_netReset">&netReset.longDesc;</div> -- PK Hans Finckh

1 0

[opensuse] rkhunter reports "no running system logging found"
by ellanios82 12 Oct '14

12 Oct '14

Hello List, root kit hunter reports that : "no running system logging found" ............... next, i tried command : # systemctl status syslog.service - but the result is : " syslog.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) " ............. How please to re-start system logging ? thanks regards ellan -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 9

[opensuse] Right click menu disappeared
by Mark Misulich 12 Oct '14

12 Oct '14

Hi, On this laptop I have three openSuse systems installed. I have 13.1 with KDE 4.13, another 13.1 with KDE Framework5, and finally 13.2 with KDE 4.14.1 installed. On both of the 13.1 systems, right clicking in any appropriate place will no longer bring up a menu list of actions. The 13.2 system right click still operates normally and brings up a menu of actions. All the touchpad configurations seem to be the same in all systems, and I haven't been able to find any settings to change to restore the right click menus in the two 13.1 systems. Does anyone have any ideas about how to fix this? Thanks, Mark -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] firefox & webcam
by Fr David Ousley 11 Oct '14

11 Oct '14

Friends -- I need to participate in a web conference. The website only supports Firefox in Linux. My problem is that Firefox will not recognize my USB webcam. The webcam is fine with cheese. In Firefox, the camera does not come on, and the web page returns "audio unavailable." It looked for audio since it could not find video. I have poked around Firefox help without finding what I need. Any suggestions on things to try? Thanks. -- Church of St Michael the Archangel Fr David Ousley 6611 Ardleigh Street Philadelphia, PA 19119 215-247-1092 davidousley(a)verizon.net -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Re: [opensuse-factory] reiserfs kernel threads present even after reiserfs kernel module is unloaded
by auxsvr＠gmail.com 11 Oct '14

11 Oct '14

On Friday 10 of October 2014 16:12:17 Andrei Borzenkov wrote: > What openSUSE version are you using? 13.1. I reported it here, because the kernel is one minor version higher than the factory one and the rest of the distribution should not affect this. I could check this on factory, but not today. -- Regards, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] updating 13.2 RC1 to final release
by Peter 11 Oct '14

11 Oct '14

I was thinking of throwing 13.2 RC1 on a redundant old laptop to test a couple of things. I'd be wanting to update it to the final release when it's ready. Can that be acheived merely by doing a zypper dup? This may be harking back to some dark age, but I recall in the past it wasn't always so straight-forward to update a beta or RC to the final release, and there was even advice against trying to go about it that way. Are there still any pitfalls to be aware of? Cheers, Peter -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4