February 2014 - openSUSE Users - openSUSE Mailing Lists

[opensuse] claws-mail 3.9.2: Getting readable non-ASCII subject line
by jdebert 05 Feb '14

05 Feb '14

OpenSuSE-12.3 Claws-Mail 3.9.2 (claws-mail-3.9.2-2.4.1.i586) The subject line is unreadable when it's text is not ASCII. Is there a reliable way to persuade claws-mail to correctly render the subject into readable text? Thanks, jd ob-acks: 1)I know that non-ASCII text in headers is not RFC compliant. 2)But such RFC compliance is irrelevant to most of the non-ASCII world. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] A tool for printing programs
by Dsant 05 Feb '14

05 Feb '14

Would you know a tool on openSUSE, for printing C/C++ program in a clever way ? If you print using kwrite <3 , you will use minimum paper ok, but functions will be randomly cut on paper :( This tool will lost space, but help program understanding by cutting program : one function per page for example :) -- (o_ //\ Dsant, from Lyon, France V_/_ forum(a)votreservice.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] QT5 has two download repository, which one ?
by Dsant 05 Feb '14

05 Feb '14

For programming using the latest stable Qt5 (not Qt4) (that is Qt 5.2 now) without downloading from Qt , which repository should I use : http://download.opensuse.org/repositories/KDE:/Qt5/ ? http://download.opensuse.org/repositories/KDE:/Qt52/ ? What does the first one contains ? Would there be a symbolic link to "always the latest stable Qt5" ? -- (o_ //\ Dsant, from Lyon, France V_/_ forum(a)votreservice.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Print to file of web page - links?
by Anton Aylward 05 Feb '14

05 Feb '14

This isn't just a firefox question ... I'm in firefox and want to do a bit more than just bookmark the page. Who knows, it might not be there when I come back! So I can save it as an HTML... Or I can cave it using a plug-in in a more condensed format Or I can print it ... But what if the links aren't explicit? Or I can print to file... But if I print to file as PDF the links, while highlighted, aren't preserved. Why not? If I create a document using LibreOffice and save that as a PDF the links I may have in there _are_ preserved. What do I need to do to my printer subsystem to make it print PDFs that preserve links? -- As with the Christian religion, the worst advertisement for Socialism is its adherents. -- George Orwell -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] Test list
by Mateusz Mielczarek 04 Feb '14

04 Feb '14

Hi, I just want to make a test, because I sent today something to other mailing group (opensuse-pl), and I don't know if they recive anything -- Best regards Mateusz Mielczarek -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 4

Re: [opensuse] seamonkey
by Patrick Shanahan 04 Feb '14

04 Feb '14

* Joe Zien <jozien(a)comcast.net> [02-03-14 20:07]: > Patrick Shanahan wrote: > >* Joe Zien <jozien(a)comcast.net> [02-03-14 17:28]: > >>I successfully installed suse 13.1 on my TkinkPad T60 and > >>I have a problem with seamonkey, get the following error when I try > >>to open it: > >Where did you get the seamonkey install and what version > I got the latest version from mozilla site when you do this, you get what you get.... > >>jozien@linux-4w99:~/seamonkey> ./seamonkey > >>XPCOMGlueLoad error for file /home/jozien/seamonkey/libxpcom.so: > >>libxul.so: cannot open shared object file: No such file or directory > >>Couldn't load XPCOM. > >>jozien@linux-4w99:~/seamonkey> > >Normally on openSUSE using openSUSE rpms there would be no > >~/<user>/seamonkey directory! > >>Don't have this problem on my other debian distros > I got the latest version from mozilla siteand they all run seamonkey > without any problems. > >You said you were using "suse", I suppose you really mean openSUSE. What > >does demian have to do with it? > > > >ps: You have not "successfully installed" seamonkey if it does not run. > I successfully installed opensuse 13.1 > > > >http://download.opensuse.org/update/13.1/x86_64/seamonkey-2.23-4.3.x86_64.r… > I downloaded > > seamonkey-2.23-4.3.x86_64.rpm and will install > > >you *really* should use packages built for the distro you utilize! Please save yourself many headaches but using packages built specifically for your distro. And please respond to list main on list. -- (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

4 4

Re: [opensuse] Need Linux based wifi-Security Camera Monitoring Setup Help
by David C. Rankin 03 Feb '14

03 Feb '14

On 01/29/2014 06:55 PM, John Andersen wrote: > Us NON-Experts say that before you spend a ton of time doing this you might want > to price pre-baked systems to see if you really want to re-invent the wheel. > http://www.amazon.com/s/ref=nb_sb_ss_c_0_16?url=search-alias%3Delectronics&… > > You can get entire systems for less than the price of the computer you would > have to buy to run this stuff. Jim, JA Thank you for your replies, I'll evaluate each. I am always torn with regard to buying a box-set or building my own. There are some many fantastic open-source projects out there, I just figured there must be a security system monitoring project somewhere. If not, how hard could it be? Take a couple of camera feeds (there has to be some basic interface to them) write a small app to capture a frame per second or two and perhaps a compressed continual audio stream (size permitting) and just record the information on an existing server. Perhaps get fancy and provide an interface where you could mux the feeds 2-up or 4-up,etc.. and be done with it for the price of the cameras. However, I'm starting from an empty pool of knowledge regarding camera capabilities, interfaces, the works, so it will be interesting to see what is out there. I'll post a write-up when I get done digesting the information. If anybody else has any thoughts on this type of setup please let me know. Thanks. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] grub 2 core.img
by Joe Zien 03 Feb '14

03 Feb '14

I installed suse 13.1 on a ThinkPad T60 and it is working fine. Suse wiped out my legacy grub in the MBR and installed grub 2, which I don't like. My grub legacy uses menu.lst to boot any distro, grub 2 uses core.img to boot distros. Where is core.img? How can I boot Suse using legacy grub? jozien -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3

[opensuse] yast2 disk - Client call failed with key not found: :CT_UNKNOWN
by Michael Hamilton 03 Feb '14

03 Feb '14

I recently upgraded to 13.1 from 12.3. On both yast2 disk is failing to start. After answering yes to the standard warning popup dialog, yast2 disk terminates. If I run yast2 disk from the command line I see the following messages: Unknown config. Invalid snapshot ''. The first message is general and occurs whenever I start any yast2 module, but doesn't seem to be causing any issues. The second message occurs when yast2 disk terminates. This machine is anything but a fresh install, and has been upgraded through several releases and has also had a change in hostname. Looking in /var/log/messages/YaST2/y2log I can see: 2014-01-08 09:39:24 <1> kosmos1(9914) [libstorage] Storage.cc(equalBackupStates):7514 lhs:expert-partitioner rhs: verbose:true 2014-01-08 09:39:24 <1> kosmos1(9914) [libstorage] Storage.cc(equalBackupStates):7564 ret:true 2014-01-08 09:39:24 <1> kosmos1(9914) [libstorage] Storage.cc(createBackupState):7448 comp:true 2014-01-08 09:39:24 <3> kosmos1(9914) [Ruby] yast/wfm.rb:86 Client call failed with key not found: :CT_UNKNOWN and backtrace ["/usr/share/YaST2/modules/StorageFields.rb:70:in `fetch'", "/usr/share/YaST2/modules/StorageFields.rb:70:in `block in IterateTargetMap'", "/usr/share/YaST2/modules/StorageFields.rb:69:in `sort!'", "/usr/share/YaST2/modules/StorageFields.rb:69:in `IterateTargetMap'", "/usr/share/YaST2/include/partitioning/ep-main.rb:363:in `MakeNavigationTree'", "/usr/share/YaST2/include/partitioning/ep-main.rb:664:in `ExpertPartitioner'", "/usr/share/YaST2/clients/inst_custom_part.rb:37:in `main'", "/usr/share/YaST2/clients/inst_custom_part.rb:42:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'", "/usr/share/YaST2/clients/inst_disk.rb:84:in `main'", "/usr/share/YaST2/clients/inst_disk.rb:105:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:71:in `CallFunction'", "/usr/share/YaST2/clients/disk_worker.rb:88:in `DiskSequence'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/fun_ref.rb:33:in `call'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/fun_ref.rb:33:in `call'", "/usr/share/YaST2/modules/CommandLine.rb:1590:in `Run'", "/usr/share/YaST2/clients/disk_worker.rb:80:in `main'", "/usr/share/YaST2/clients/disk_worker.rb:158:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:77:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:67:in `call'", "/usr/share/YaST2/clients/disk.rb:85:in `main'", "/usr/share/YaST2/clients/disk.rb:103:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.0.0/yast/wfm.rb:84:in `run_client'"] 2014-01-08 09:39:24 <1> kosmos1(9914) [Interpreter] clients/inst_disk.rb:84 Called YaST client returned. 2014-01-08 09:39:24 <2> kosmos1(9914) [Ruby] yast/convert.rb:54 Cannot convert FalseClass from 'any' to 'symbol' 2014-01-08 09:39:24 <1> kosmos1(9914) [Ruby] clients/inst_disk.rb:99 end inst_disk ret:nil 2014-01-08 09:39:24 <1> kosmos1(9914) [Interpreter] clients/disk_worker.rb:88 Called YaST client returned. 2 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 1

[opensuse] dd on an SD card gives: Read-only file system
by Freek de Kruijf 03 Feb '14

03 Feb '14

I have an SD card on /dev/sde. The command "findmnt -l" does not show anything mounted on /dev/sde*'. I am the root user. "ls -l /dev/sde*" shows: brw-rw---- 1 root disk 8, 64 Feb 1 13:43 /dev/sde brw-rw---- 1 root disk 8, 65 Feb 1 13:43 /dev/sde1 So apparently the device is writable. I checked the lock switch on the SD card which is unlocked. After that I want to write an image on the SD card using dd with of=/dev/sde, however I always get: dd: failed to open ‘/dev/sde’: Read-only file system I am using openSUSE 13.1, which is fully updated. When I mount the SD card, which is mounted as a vfat device, I am also unable to write on the device. Any suggestions? -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 16