January 2016 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] acpid requires systemd?
by Felix Miata 25 Apr '24

25 Apr '24

Can this be true? If so, why? Zypper won't let me upgrade acpid without breakage unless systemd is installed too. I have systemd locked out, as I'd rather test things I can understand in Factory, not major overhaul stuff. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory+help(a)opensuse.org

4 3

[opensuse-factory] How can calibre be allowed access through YaST firewall?
by Chan Ju Ping 24 Sep '16

24 Sep '16

Unlike rsync, or KDE Connect, there is no option to automatically allow the Calibre ebook manager to open ports so external devices can connect to it. So far, my solution has been to disable the firewall before connecting my device to Calibre via the Calibre Companion app on Android. For those unfamiliar with the process, Calibre Companion can sync ebooks from the desktop's library to the Android device's library, thus eliminating the need for wires and further organization of books. If I know I am using port 9090 for Calibre, is there a way to allow this connection in the Firewall? Has anyone else attempted this setup? Running netstat shows this additional parameter enabled when my tablet is connected to the computer. tcp 0 0 10.42.0.1%2457529:39858 10.42.0.250%328:sesi-lm ESTABLISHED

3 8

[opensuse-factory] btrfs fun / disk full
by Christian Boltz 25 Feb '16

25 Feb '16

Hello, I just had an interesting[tm] problem - updating to the latest tumbleweed failed at random places. It turned out that my btrfs / partition was full. Not with df -h (which reported some GB free), but "btrfs fi show" showed 100% usage. (Sorry for not including the exact output - I didn't save it.) I moved 15 GB of libvirt images to a different partition and deleted some old snapshots, but both didn't help. After some searching (and temporaryly breaking my /, which I could luckily repair with snapper rollback), I found out [1] that I should run btrfs balance start / -dlimit=3 which freed quite some space. Another run freed even more space, so I decided to run it without the limit: btrfs balance start / After that, I'm down to # btrfs fi show Label: none uuid: 9f4a918d-fcd4-45d3-a1dc-7b887300eabc Total devices 1 FS bytes used 22.91GiB devid 1 size 50.00GiB used 25.31GiB path /dev/mapper/cboltz-root Even if you re-add the 15 GB libvirt images in the calculation, this still means the rebalance freed about 10 GB = 20% of the partition size. So the good news is that I could solve the problem. The bad news is that it happened at all. Should there be a cronjob that does the rebalancing or other btrfs maintenance regularly? Bonus question: snapper list shows that snapshot #1 ("first root filesystem") is still kept. Is this snapshot needed for something, or can I safely delete it? BTW: a funny detail is: # btrfs balance start / WARNING: Full balance without filters requested. This operation is very intense and takes potentially very long. It is recommended to use the balance filters to narrow down the balanced data. Use 'btrfs balance start --full-balance' option to skip this warning. The operation printf will start in 10 seconds. ^^^^^^ I slightly doubt "printf" is the word that was wanted here ;-) Regards, Christian Boltz [1] https://btrfs.wiki.kernel.org/index.php/FAQ#Help.21_I_ran_out_of_disk_space… -- > New Versions usually bring bug fixes and security fixes. ...and new bugs. Funny how people tend to forget about that. [> Michael Melcher and Michal Kubecek in opensuse-factory] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

13 22

[opensuse-factory] texlive 2015
by Marguerite Su 22 Feb '16

22 Feb '16

Hi, I managed to update texlive 20150521: https://build.opensuse.org/package/show/home:MargueriteSu:branches:Publishi… it builds successfully for Leap and TW. here are some leaf problems I need help: 1. where could I find changelog for texlive 2015? I mean major changes 2. openSUSE 13.2 won't build due to http://paste.opensuse.org/68437610 but texlive 2015 has supported poppler 0.26. so can anyone have a look at it? My C skill is not enough for it. 3. in specfile, there're many version tags with svn commit number. eg: %package a2ping-bin Version: %{texlive_version}.%{texlive_release}.svn27321 how did these different "svn27321" determined? I could find any .svn inside texlive 2015 source. Thanks for the help! And texlive 2015 is on its way. Marguerite -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

[opensuse-factory] After Kmail upgrade, KWallet no longer using GPG encryption
by Chan Ju Ping 10 Feb '16

10 Feb '16

One other thing that may have been left out of upgrade consideration is importing previous security settings as well. I always do an initial setup of Kwallet with GPG encryption, though in the latest upgrade, this has been automatically replaced with the simple passphrase method. What would be the best way to upgrade and assign the credentials in Kmail to GPG (I still have a laptop running TW that is still on Kmail4 until I figure out all the issues on my desktop with Kmail5)? For my Kmail5 setup, how to I re-enable GPG-level protection for my accounts?

4 13

[opensuse-factory] digikam-libs conflicts when updating Tumbleweed 20160121
by Thomas Wagner 09 Feb '16

09 Feb '16

Hi I have Tumbleweed 20160121 and just did a "zypper up". It brings up the following error. 8 Dateikonflikte festgestellt: File /usr/lib64/libkdcraw.so.23.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkdcraw23-15.08.3-1.3.x86_64(@System) File /usr/lib64/libkexiv2.so.11.3.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkexiv2-11-15.08.3-2.1.x86_64(@System) File /usr/lib64/libkface.so.3.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkface3-15.08.3-1.1.x86_64(@System) File /usr/lib64/libkgeomap.so.2.1.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkgeomap2-15.08.3-1.1.x86_64(@System) File /usr/lib64/libkipi.so.11.1.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkipi11-15.08.3-1.1.x86_64(@System) File /usr/lib64/libksane.so.0.2.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libksane0-15.08.3-1.2.x86_64(@System) File /usr/lib64/libmediawiki.so.1.0.0 from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libmediawiki1-4.13.0-2.1.x86_64(@System) File /usr/share/kde4/servicetypes/kipiplugin.desktop from install of digikam-libs-4.14.0-2.1.x86_64(repo-oss) conflicts with file from package libkipi11-15.08.3-1.1.x86_64(@System) How to fix this double packaged files? best regards Thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

8 22

[opensuse-factory] Tumbleweed not booting for Radeon R9 380 card
by Chan Ju Ping 04 Feb '16

04 Feb '16

I just installed a new Radeon R9 380 card today, and tried booting into Tumbleweed. Grub loaded without issue but when it was suppose to show the screen to input my LUKS password, only the following error messages appear: EDAC sbridge: ECC is disabled. Aborting EDAC sbridge: Couldn't find mci handler amdgpu 0000:03:00.0: Invalid ROM contents I have Ubuntu loaded in a separate partition to boot into which also briefly shows something similar, but immediately loads lightdm without issue. I would not the Ubuntu installation is running the proprietary drivers, but not Tumbleweed. What packages am I suppose to install to get the card working properly on Tumbleweed?

4 9

[opensuse-factory] Requesting new devel projects for Ceph and openATTIC
by Nathan Cutler 01 Feb '16

01 Feb '16

Hi Factory ML: Ceph[1] is a unified, distributed storage system designed for excellent performance, reliability and scalability. openATTIC[2] is a storage management and monitoring tool that our team is currently in the process of adapting to work with Ceph clusters. My colleagues and I are very interested to submit the latest, greatest versions of these two interesting pieces of software to openSUSE:Factory. Projects are already created: https://build.opensuse.org/project/show/filesystems:ceph https://build.opensuse.org/project/show/filesystems:openATTIC What do we need to do to obtain "Factory devel project" status for these projects? Thanks in advance, Nathan Cutler [1] http://ceph.com [2] http://openattic.org/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 3

[opensuse-factory] Nginx Mainline (1.9.x)
by Ibrahim M. Ghazal 01 Feb '16

01 Feb '16

I'm curious, why does Tumbleweed have Nginx "stable" (1.8.x) and not "mainline" (1.9.x)? >From https://www.nginx.com/blog/nginx-1-6-1-7-released/ : > Note that stable does not mean more reliable or more bug-free. In fact, the mainline is generally regarded as more reliable because we port all bug fixes to it, and not just critical fixes as for the stable branch. And > We recommend that in general you deploy the NGINX mainline branch at all times. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 8

[opensuse-factory] Do we want the encryption method selector during install?
by Ancor Gonzalez Sosa 01 Feb '16

01 Feb '16

The changes described (screenshots included) in this pull request are already in their way to Tumbleweed (sr#356569) https://github.com/yast/yast-users/pull/84 So the question now is - should we adapt the control.xml file for Tumbleweed or is it fine to not offer the selection of password encryption method during installation anymore? In case you believe it should be there, what do you prefer - the verbose "users" proposal or the more concrete "users_encryption" one? Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 4