April 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] receiving files via bluetooth fails
by Olaf Hering 24 Sep '17

24 Sep '17

Some months ago it was possible to receive files via bluetooth with TW. But since some weeks that fails for me. I waited for GNOME 3.20 and the new bluez in the hope it will fix itself, but the failure remains: Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff) Apr 05 18:01:28 probook obexd[3042]: CONNECT(0x0), (null)(0x0) Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), (null)(0xffffffff) Apr 05 18:01:32 probook obexd[3042]: open(/home/olaf/.cache/obexd/GSIBFY): No such file or directory (2) Apr 05 18:01:32 probook obexd[3042]: PUT(0x2), NOT_FOUND(0x44) Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff) Apr 05 18:01:32 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20) Apr 05 18:01:32 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) Apr 05 18:01:32 probook obexd[3042]: disconnected: Transport got disconnected Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0xffffffff) Apr 05 18:02:42 probook obexd[3042]: CONNECT(0x0), (null)(0x0) Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), (null)(0xffffffff) Apr 05 18:02:42 probook obexd[3042]: open(/home/olaf/.cache/obexd/1OLQFY): Operation not permitted (1) Apr 05 18:02:42 probook obexd[3042]: PUT(0x2), FORBIDDEN(0x43) Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), (null)(0xffffffff) Apr 05 18:02:42 probook obexd[3042]: DISCONNECT(0x1), SUCCESS(0x20) Apr 05 18:02:42 probook bluetoothd[1520]: Unable to get io data for Object Push: getpeername: Transport endpoint is not connected (107) Apr 05 18:02:42 probook obexd[3042]: disconnected: Transport got disconnected First I tried to remove /home/olaf/.cache/obexd, but nothing seems to feel responsible to create this dir as seen with the first error. Then I created it with mkdir -m07777, and that just gives the EPERM error as before. strace shows that it gets some "forbidden" from dbus. Is receiving files working for anyone else? Also the rfkill thing does not work reliable. NetworkManager finds the device according to syslog, but the GNOME bluetooth thing finds nothing. Something softblocks it: root@probook:~ # hciconfig -a hci0 reset Can't init device hci0: Operation not possible due to RF-kill (132) root@probook:~ # rfkill list all 0: hp-wifi: Wireless LAN Soft blocked: no Hard blocked: yes 1: hp-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: yes Hard blocked: no Need to run 'rfkill unblock 4' manually to get it going. Once that it done its appearently possible to use the UMTS, and sending a file works as well. Olaf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 5

[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] Transitioning to GCC 6
by Richard Biener 25 Jul '16

25 Jul '16

You may have noticed that GCC 6 packages appeared in Factory (but gcc used for building packages still points to GCC 5). Somewhen in January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used to build packages. The status of that is that it depends on the glibc update pending in Staging:B and it still requires fixing a few packages, mostly -Werror related. There was a point in time where openQA was green for x86_64 (and Minimal-X). Once Staging:B has been accepted I'll formally submit an update to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6. That staging can nevertheless be used to look at the current FAILs which are build failed cluster-glue failed elfutils failed espeak failed gdb failed jack failed libyui failed llvm failed mozilla-nss failed pesign failed python3-base failed xen failed and can also be caused by the glibc update which I pulled into Staging:Gcc6. Any help is appreciated. Richard. -- Richard Biener <rguenther(a)suse.de> SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 21

[opensuse-factory] Planned release schedule for Leap 42.2
by Ludwig Nussel 20 Jun '16

20 Jun '16

Hi, Time flies, so let's start planning the schedule for Leap 42.2. The current version 42.1 is based on SLE12 SP1 and 42.2 is meant to be based on SP2¹. SLE12 SP2 is expected to reach the beta phase mid of May which means we'll get the package sources in OBS then. That in turn will allow us to start building Leap on top. My plan would be to have a first Alpha end of May based on 42.1 sources with the SLE bits updated to SP2. The next snapshot should be before OSC in June and another one in July. I'd aim for the the first Beta last week of August, followed by Beta2 around September 21st. RC1 would then be Oct 6, followed by RC2 Oct 18. GM Oct 27 so we can release November 2nd. cu Ludwig [1] https://en.opensuse.org/Portal:42.1 -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 17

[opensuse-factory] Broken -fsanitize=address in local installation
by Cristian Rodríguez 20 May '16

20 May '16

Hi: In my local workstation, I have both gcc5 and gcc6 installed from the devel:gcc repository.. since maybe a month.. ASAN is broken and I can't figure out how to fix it. cat t.c #include <stdio.h> int main(void) { return 0; } gcc-5 -fsanitize=address t.c ➜ ~ ./a.out ==59605==AddressSanitizer CHECK failed: ../../../../libsanitizer/asan/asan_rtl.cc:556 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) <empty stack> same result if I use GCC-6. any pointers about what exactly I screwed up ? ;) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 4

[opensuse-factory] paving the road for Leap 42.2
by Ludwig Nussel 09 May '16

09 May '16

Hi, As some have already noticed, we have an openSUSE:Leap:42.2 project in OBS which deserves some explanation. There's not much to see there yet though. I've just finished to bootstrap ring 0 (Boostrap), 1 (X) and 2 (Desktops). My next goal is to prepare openQA to get working tests again. Starting with a green openQA is always easier than having everything broken. So assuming 42.1 passed openQA just fine the copy that is called 42.2 should be comparatively easy to get to a testable state again. After that I'll set up staging projects and start integrating the maintenance updates from 42.1. From there on we should be ready to integrate the SLE12SP2 sources once they are available in OBS. Meanwhile also some work has been going on with the translations. https://l10n.opensuse.org/ was updated to Weblate 2.5 which includes features requested by various openSUSE translators. Weblate works best when it can work with git directly. So the translation files that were so far hosted on svn.opensuse.org need to be moved to git repos. That work usually requires some programming and packaging skills to clean up and improve the tools and packages involved. Help is appreciated there. I've opened a set up tasks in redmine to keep track of the progress: https://progress.opensuse.org/issues/11334 Feel free to jump in where you see fit. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

6 9

[opensuse-factory] Can't activate VPN
by Chan Ju Ping 04 May '16

04 May '16

I can't seem to activate any of my VPN connections since the massive update. Is anyone experiencing the same issue?

14 23

[opensuse-factory] Community Release Team for Leap 42.2
by Tomas Chvatal 03 May '16

03 May '16

Hello everyone, With the upcoming Leap release the Board is working to help Ludwig produce the best release ever, or to be honest just better than the previous one. We have an established task list of items that needed to be done prior release of distribution, like Leap 42.1 is here [1]. In the past, these tasks were then distributed among the SUSE employed openSUSE team which tried to incorporate community and in the end make sure that everything gets done. Now things are different. We would like the community to be directly responsible for ensuring these tasks get carried out. To accomplish this we intend to create a full team of people taking care about what needs to be done for the release. We expect the people in this "Community Release Team" to be the ones responsible for the tasks in their respective areas of responsibility. We are not necessarily expecting these people to directly do all the tasks, but it will be their responsibility that they get done. They should work towards encouraging more contributors to work with them on these tasks, if necessary lifting a pitchfork and prod people to ensure all the tasks are done, or stepping up and doing the tasks alone as a last resort. The tasks can generally be split in following areas: * Marketing * Design * Infrastructure * Documentation * Translations * QA To avoid expanding this mail too much brainstorming/descriptions are attached in rst formatted file. It is not complete listing of the tasks, those are mostly in the progress [1] and if anything else happen to be needed/invented by the guys volunteering to do this it will be expanded. If you are interested on taking the lead on any of these areas and joining this new "Community Release Team" please let Ludwig and the board know. Cheers Tom + Rest of the board [1] http://tinyurl.com/grg5szf

4 3

[opensuse-factory] Tumbleweed distro date
by Karl Ove Hufthammer 02 May '16

02 May '16

When I report a bug in KDE using DrKonqi, it inserts the following information at the top of the bug report: Distribution: "openSUSE Tumbleweed (20160117) (x86_64)" Where is this date (2016-01-17) taken from, and what does it mean? (Note that I’m using the latest release of Tumbleweed, *not* one from January 2016.) -- Karl Ove Hufthammer -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

9 11