March 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] Leap 42.2 'geany.spec' broken, %if %{prefer_gtk2}, now mixes gtk2 + gtk3
by David C. Rankin 04 Mar '17

04 Mar '17

All, Geany currently builds with gtk3 in Leap and looks horrible regardless of theme. Talked to the devs on github and they said building against gtk2 would provide the traditional interface. The suse geany.spec supports building against gtk2 by passing the 'prefer_gtk2' parameter. However, the suse geany.spec is broken as passing 'prefer_gtk2' results in a build that includes both gtk2 and gtk3 -- which of course will not run. For example setting '%define prefer_gtk2 1' in the spec, results in a successful build: $ rpmbuild -ba geany.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.SKIeFq + umask 022 + cd /home/david/rpmbuild/BUILD + cd /home/david/rpmbuild/BUILD + rm -rf geany-1.29 + /usr/bin/bzip2 -dc /home/david/rpmbuild/SOURCES/geany-1.29.tar.bz2 + /bin/tar -xf - + STATUS=0 <snip> ------------------------------------------ Install Geany in : /usr Using GTK version : 2.24.31 Enable binary relocation : no Build with plugin support : yes Use (UNIX domain) socket support : yes Use virtual terminal support : yes Build HTML documentation : yes Build PDF documentation : no Build API documentation : yes Generate GtkDoc header : yes Configuration is done OK. + make make all-recursive <snip> Wrote: /home/david/rpmbuild/SRPMS/geany-1.29-39.1.src.rpm Wrote: /home/david/rpmbuild/RPMS/x86_64/geany-1.29-39.1.x86_64.rpm Wrote: /home/david/rpmbuild/RPMS/noarch/geany-lang-1.29-39.1.noarch.rpm Wrote: /home/david/rpmbuild/RPMS/x86_64/geany-devel-1.29-39.1.x86_64.rpm Wrote: /home/david/rpmbuild/RPMS/x86_64/libgeany0-1.29-39.1.x86_64.rpm Wrote: /home/david/rpmbuild/RPMS/x86_64/geany-doc-1.29-39.1.x86_64.rpm Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.JACvkI + umask 022 + cd /home/david/rpmbuild/BUILD + cd geany-1.29 + /usr/bin/rm -rf /home/david/rpmbuild/BUILDROOT/geany-1.29-39.1.x86_64 + rm -rf filelists Then when you attempt to start geany: $ geany (geany:7704): Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported Trace/breakpoint trap (core dumped) WTF?? Why is GTK+3 in the same process the spec file told to build against gtk2?? -- 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

1 1

Re: [opensuse] Very basic dd question
by Christopher Myers 04 Mar '17

04 Mar '17

>>> Stevens <fred-n-sandy(a)myrhinomail.com> 03/01/17 9:17 AM >>> > On 03/01/2017 08:25 AM, Christopher Myers wrote: > > > > > > In case it helps, these are notes that I have on resizing .img files created by dd: > > > > > > > <snip> > > > > Shrink the partition down using gparted. > > > That's where the train comes off the tracks, as my gparted won't shrink > a partition. Runs for a while, gives me an option for converting to > FAT32 instead of FAT16, yada yada yada then BOOM! a box pops up saying > I've found a gparted bug. So, no gparted shrink here. At least, not for > a FAT16 partition. I haven't tried anything else because it's FAT16 I'm > working with, so if it works with something else it matters not. > Now, if this solution were as simple as dd'ing the first 170MB of the > image, that would be great because there is only about 150GB +/- of data > but I suspect that all OSes put something at the end of a partition > instead of just from the front forward so only copying the front will > lose the back and render the image useless. Or do I have that wrong? > Later, and thanks. > Fred Hmm, I'm not really sure, but maybe others will have some input? I do know that the reason that you need to shrink the partition before shrinking the image is so that the data will all get consolidated at the beginning of the disk, otherwise you'll potentially have files throughout the partition that'd get chopped out. But I'm not sure of better ways to shrink the partition, especially on the image file. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

[opensuse] Plymouth + NVidia = No Boot splash
by Bjarne Örn Hansen 04 Mar '17

04 Mar '17

Hej, I got the idea that installing plymouth, would give me a "nicer" bootsplash. So, I installed it ... but since that, the only thing I get during boot is a blinking underscore. Been searching the net, but haven't found any information on how to fix this. Anybody else getting the same thing? Any solutions? // Bjarne -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 3

Re: [opensuse] TW: LibreOffice Calc : Negative Numbers in Red not working
by ellanios82 04 Mar '17

04 Mar '17

On 03/03/17 15:18, Patrick Shanahan wrote: Thank you kindly Patrick for hosting my sample file at : http://wahoo.no-ip.org/~paka/Negative_Numbers_all_Black.ods > let me know when to take it down. thanks v.m. : 3 days will be ample > btw: your negative numbers show as red for me > - as Carlos suggested : maybe this might be a Greece Locale problem , however, OpenOffice sees negative Numbers in Red all right, here ..... thanks ... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 15

Re: [opensuse] Very basic dd question
by Stevens 04 Mar '17

04 Mar '17

An update: The dd command as suggested by Greg worked fine, I was able to take the original 2 good hdds (or working pulls w/ os on them) and back them up to a couple of files in the temp dir, then write back out to a couple of unpartitioned drives of equal or larger size. I tried to resize with gparted but it fails to resize and I don't have any other tool (yet) to do that. Orig hdd is 1 GB with about 110MB of data in FAT16 partition and the other is about that size with maybe a bit more data. One has Win 3.11 and the other is Win95 (I said it was old crap). Issue is 3 spare drives from 172MB to 800MB size that I cannot use until I get the copied partition resized down to 172MB. The copied partitions are on drives that are too thick to fit into his laptops. It's always something ... Thanks, all. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

8 13

[opensuse] file conflict error message from zypper
by Richmond 03 Mar '17

03 Mar '17

I am puzzled by this error message because 1) I would not expect a development library to have anything which conflicted with a run time library. (They are from the same vendor). Although I am no expert in such matters. 2) My only options were yes or no, and accepting "no" meant nothing at all was installed. Maybe it should be possible to skip? as there were some 500 packages to update. This is opensuse tumbleweed running on a 32 bit laptop. The offending library is from/used by LLVM. File /usr/lib/libomp.so from install of libomp3_9-devel-3.9.1-6.2.i586 (Main Repository (OSS)) conflicts with file from package libomp-3.8.1-1.1.i586 (@System) File conflicts happen when two packages attempt to install files with the same name but diff\ erent contents. If you continue, conflicting files will be replaced losing the previous cont\ ent. Continue? [yes/no] (no): Problem occured during or after installation or removal of packages: Installation aborted by user -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 1

[opensuse] TW: LibreOffice Calc : Negative Numbers in Red not working
by ellanios82 03 Mar '17

03 Mar '17

Hello List , TW - LO Calc refuses to display Negative Numbers in Red : Formatting Cell to display Negative Numbers in Red results in Black , not Red any ideas ? thanks .... -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 7

[opensuse] OpenBoard 1.3.4 now available as package
by Thorsten Bro 03 Mar '17

03 Mar '17

Hi Josep, it took a while, but due to me using the OpenBoard-Software in my HackWeek-Project, i pushed this topic a bit and got help from our packaging and Qt experts - so thanks to adamm, darix and danimo - we have now a well working OpenBoard package available in the Education project. My hackweek project: https://hackweek.suse.com/projects/geekoscreen-building-an-open-source-base… Try it out: https://build.opensuse.org/package/show?project=Education&package=OpenBoard https://software.opensuse.org/package/OpenBoard Cheers, Thorsten -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 2

[opensuse] the linux users guide to dismissing new technology
by nicholas 02 Mar '17

02 Mar '17

any change to technology is a threat to your existing knowledge and skills and should be rejected immediately. the more convoluted the existing technology is the better, it gives you and edge over others, which you need to defend (eg init). here is an incomplete list of potential stratergies: [1] divine truth: a useful prescript e.g. "a tool should do 1 thing and do it well" is a divine truth. it is not subject time, context, evidence, data or reasoning. [like the 10 commandments] (you can use divine truth to immediatly dismiss systemd irespective of technical arguments). [2] if the new technology doesnt work in the same way as the old, it is flawed. since the new tech requires new knowledge, it is obviously more complex QED. [be carefull not to apply this to windows vs linux] [3] dismiss any new features as pointless and unneeded. [4] faults: any shortcoming of new tech (be truth or hype) should be vocalised extensively. try to frame an argument such that the old tech has no problems. [5] avoid data, evidence, reasoning and context: rely on rumours, anecdotes, fud, comments on reddit, appeals to emotion and truthiness. [6] give the new tech whipping boy status: any problem for which a diagnosis does not exist should be attributed to the new tech. [7] condemn the new tech based on partial knowledge you havnt verified, and use this to form an apparently rational conclusion (e.g. systemd timer limitations) lets take an example: OP: "i had a problem, I dont know what it was, I used the wrong tools to diagnose it, ignored any recommendations on how to fix it, did something i didnt understand, and it still didnt work. whats more the same thing happened on all 5 systems which is statistically impossible if considered as independent (non correlated) failures" you now have all the hard evidence you need, and can let rip: [a] "the same thing happened to me - this is proof the system is rubbish" [b] "how could you ship a system that allows such a thing to occur" [c] "there is some fud on the internet from 5 years ago showing how bad the system is, whats wrong with you people" [d] "any tech that requires understanding is no good for home users" [ignoring the fact that the linux ecosystem itself fails under the premisses of the argument] -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 5

[opensuse] about: fcitx
by stakanov 02 Mar '17

02 Mar '17

I read today in openfate that for SP3 fcitx is deprecated, the author of the mail in question did state that, from his point of view it is not necessary to patch it any more. I did not understand well the issue. Is fcitx still in development or is it deprecated only for the plasma4 version maybe? If it is deprecated tout court, is it still safe to use it? What substitutes in this eventually fcitx. Are we back to ibus? I am quite strongly using fcitx for mandarine and am running currently 42.2. A part of a problem with the kde layout chooser, it words. That said, I understood the problem was again qt webkit (as the version 5 was not ready and fcitx relies on it. Thank you for making me understand. The feature in FATE is: Feature #322611 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0