openSUSE Factory February 2016

factory@lists.opensuse.org

144 participants
130 discussions

[opensuse-factory] How can calibre be allowed access through YaST firewall?

by Chan Ju Ping

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

4 years, 10 months

[opensuse-factory] Too many unmaintained packages in Tumbleweed

by Dominique Leuenberger / DimStar

Hi all, as a provocative* counter to the thread that we have too few packages in Tumbleweed, I would like to raise (again) awareness that I would also appreciate if people would take care of the stuff that actually IS in Tumbleweed. Getting a package IN there is not as difficult as some seem to believe, but I would like to stress that this is no hit'n'run game. Currently, TW keeps on having a rough 50 packages in failing state (some change here and there, some stay forever). Emails are sent after 7 days of failure - so I will keep this mail here 'short' to stuff failing for > 10 days (having given people a chance to read the mails). Packages with pending submissions to Factory are also excluded. So, this leaves us with this list of packages that still is in need of handling: Error python3-jupyter_ipyparallel devel:languages:python3 Fails for 11 days: Unknown build failure Error python3-jupyter_ipython-doc devel:languages:python3 Fails for 11 days: Unknown build failure Current sources were declined: request 358732 Error pocl science Fails for 11 days: Unknown build failure Error python-jupyter_console devel:languages:python Fails for 15 days: Unknown build failure Error fcitx M17N Fails for 15 days: Unknown build failure Error mipv6d network Fails for 15 days: Unknown build failure Error ksaneplugin KDE:Applications Fails for 18 days: Unknown build failure Error python-jupyter_nbconvert devel:languages:python Fai ls for 19 days: Unknown build failure Error python3-jupyter_notebook devel:languages:python3 Fa ils for 19 days: Unknown build failure Error python-jupyter_nbformat devel:languages:python Fail s for 19 days: Unknown build failure Error python-jupyter_qtconsole devel:languages:python Fai ls for 19 days: Unknown build failure Error python-jupyter_core devel:languages:python Fails for 19 days: Unknown build failure Error golang-googlecode-log4go devel:languages:go Fails for 22 days: Unknown build failure Error shim devel:openSUSE:Factory Fails for 23 days: Unknown build failure Error python3-SQLAlchemy devel:languages:python3 Fails for 23 days: Unknown build failure Error tomahawk KDE:Extra Fails for 30 days: Unknown build failure Error leechcraft network Fails for 30 days: Unknown build failure Request <a href="/request/show/358049">358049</a> to network Error python-SQLAlchemy devel:languages:python Fails for 30 days: Unknown build failure Error qsapecng electronics Fails for 33 days: Unknown build failure Error ASL science Fails for 34 days: Unknown build failure Request <a href="/request/show/358788">358788</a> to science Error gtksourceview-sharp2 Mono:Factory Fails for 43 days: Unknown build failure Error python3-flit devel:languages:python3 Fails for 47 days: Unknown build failure Error python-urllib3 devel:languages:python Fails for 49 days: Unknown build failure Current sources were declined: request 352092 Error scantailor graphics Fails for 76 days: Unknown build failure Error pam_pkcs11 security:chipcard Fails for 116 days: Unknown build failure Request <a href="/request/show/358604">358604</a> to security:chipcard Error klatexformula Publishing Fails for 127 days: Unknown build failure Error kde3-celestia KDE:KDE3 Fails for 136 days: Unknown build failure Current sources were declined: request 342132 Error krb5-appl network Fails for 140 days: Unknown build failure Error perl-Test-CheckChanges devel:languages:perl Fails for 169 days: Unknown build failure Error python-sure devel:languages:python Fails for 184 days: Unknown build failure Different sources in devel project (since 5 months) Error terminology-theme-openSUSE-oliveleaf X11:Enlightenment:Fac tory Fails for 187 days: Unknown build failure Error enlightenment-theme-openSUSE-oliveleaf X11:Enlightenment:F actory Fails for 187 days: Unknown build failure Error enlightenment-theme-openSUSE-ice X11:Enlightenment:Factory Fails for 187 days: Unknown build failure Error enlightenment-theme-openSUSE-bluegreen X11:Enlightenment:F actory Fails for 187 days: Unknown build failure Error enlightenment-theme-openSUSE X11:Enlightenment:Factory Fails for 187 days: Unknown build failure Different changes in devel project (since about 2 months) Error kross-interpreters KDE:Distro:Factory Fails for 236 days: ruby.h:585:55: error: '__builtin_choose_expr' was not declared in this scope Error kdegraphics3 KDE:KDE3 Fails for 236 days: kmultipage.h:309: undefined reference to `DocumentPageCache::sizeOfPage(PageNumber const&) const' Different sources in devel project (since 8 months) Error racket devel:languages:misc Fails for 236 days: Unknown build failure (That's 38 packages) I'd appreciate to get fixes for those as well. Cheers, Dominique * the provocation is not against the idea of the contrib repo per se. If somebody wants to take this on and chase maintainers, be prepared to invest a lot of time. This message merely wants to point out that even in openSUSE:Factory we end up with broken stuff - and that's only build broken stuff... some stuff is not installable, some stuff not runnable. openQA is very limited in its scope -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

[opensuse-factory] device notifier settings

by Patrick Shanahan

Just did an update which included: akregator5-15.12.1-34.4.x86_64 kmail5-15.12.1-34.4.x86_64 kaddressbook5-15.12.1-34.4.x86_64 korganizer5-15.12.1-34.4.x86_64 kontact5-15.12.1-34.4.x86_64 knotes5-15.12.1-34.4.x86_64 kdepim-15.12.1-34.4.x86_64 libkdepim-15.12.1-34.4.x86_64 konqueror-15.12.1-7.4.x86_64 konqueror-plugins-15.12.1-7.4.x86_64 kdebase4-libkonq-15.12.1-7.4.x86_64 akonadi_resources-15.12.1-34.4.x86_64 ... And now the device notifier which is set to "Removable devices only" shows \ and home partitions on my ssd drive ???? Does this need a bug report or ....? tks -- (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-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

[opensuse-factory] Changes to OpenSUSE Leap Release Management

by Olaf Kirch

Dear all, I would like to announce a change to the Release Management for OpenSUSE Leap. Effective March 1st, the torch will pass from Coolo to Ludwig Nussel. I think even if you were just on the side lines of the openSUSE community in the past years, you will not need a lengthy explanation of who they are and how they have contributed to openSUSE :-) Going forward, Coolo wants to focus more on establishing new practices around test automation, particularly in the context of openqa. Ludwig will assume the responsibility of supporting the community from the SUSE side in delivering openSUSE Leap releases. Tumbleweed stays in the able hands of Dominique Leuenberger. Please join me in thanking Coolo for his eminent contributions in supporting and shaping openSUSE, and in wishing Ludwig a successful start in his new role. Sincerely, Olaf Kirch -- Olaf Kirch - Director SUSE Linux Enterprise; R&D (okir(a)suse.com) SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, 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

5 years, 4 months

[opensuse-factory] USB mouse not working after boot beginning from kernel 4.4.0

by René Krell

Hardware: HP ZBook 15 G2, Logitech M-UAS 144 After the big drawback beginning from kernel 3.19, when nouveau began to be broken for the above hardware (until now), there is another one, introduced with kernel 4.4.0 in Tumbleweed: After boot/reboot, the connected USB mouse does not initially work in both cases, connected to the docking station and connected directly to the notebook. After disconnecting and reconnecting it physically the mouse works immediately. Sometimes I have been noticing the same behavior for the USB keyboard, but not everytime. I hadn't have this behavior before 4.4.0. Still not solved for 4.4.1. I cannot guarantee that this happens along with another update that came beside to kernel 4.4.0, usually I do a 'zypper dup'. Using sddm as display manager. In /var/log/messages I haven't found anything suspect, the USB devices are initialized and the mouse is actually recognized but does not work after this one: 2016-02-24T14:01:22.775406+01:00 rkrell kernel: [ 5.821627] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821642] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821643] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:01:22.775408+01:00 rkrell kernel: [ 5.821645] usb 3-2: Manufacturer: Logitech 2016-02-24T14:01:22.775409+01:00 rkrell kernel: [ 5.821850] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes The USB keyboard works already in this state. After disconnecting and connecting I get: 2016-02-24T14:02:14.951655+01:00 rkrell kernel: [ 60.981778] usb 3-2: USB disconnect, device number 3 2016-02-24T14:02:20.943684+01:00 rkrell kernel: [ 66.972056] usb 3-2: new low-speed USB device number 9 using xhci_hcd 2016-02-24T14:02:21.131609+01:00 rkrell kernel: [ 67.161892] usb 3-2: New USB device found, idVendor=046d, idProduct=c062 2016-02-24T14:02:21.131628+01:00 rkrell kernel: [ 67.161900] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2016-02-24T14:02:21.131630+01:00 rkrell kernel: [ 67.161904] usb 3-2: Product: USB Laser Mouse 2016-02-24T14:02:21.131632+01:00 rkrell kernel: [ 67.161906] usb 3-2: Manufacturer: Logitech 2016-02-24T14:02:21.131633+01:00 rkrell kernel: [ 67.162262] usb 3-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes 2016-02-24T14:02:21.135598+01:00 rkrell kernel: [ 67.167613] input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:14.0/usb3/3-2/3-2:1.0/0003:046D:C 062.0003/input/input28 2016-02-24T14:02:21.135620+01:00 rkrell kernel: [ 67.167989] hid-generic 0003:046D:C062.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Laser Mouse] o n usb-0000:00:14.0-2/input0 and the mouse is functional immediately. Any further victim of this bug, hint, is this a known problem or is there a workaround? René -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

[opensuse-factory] Failure to connect to WPA (PEAP) network on start-up

by Chan Ju Ping

On start-up, the WiFi notification always shows a failure to connect to this particular network in my university which uses WPA (PEAP) encryption. But after it reports failing to connect on start-up, it eventually connects to the network automatically. This would be a non-issue, however, KMail thinks this means the server is unavailable and my email accounts are not automatically synced, even after the establishment of a stable wireless connection. I have missed a few days worth of emails at times before I realised what was happening. My current workaround this problem is to manually restart the connection to my email servers in KMail though it would be nice to figure out what the possible root problem is. Here's the output of "lspci -vv -s 02:00.0" 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Dual Band Wireless-AC 7260 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 46 Region 0: Memory at f7c00000 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: 00000000fee0100c Data: 4162 Capabilities: [40] Express (v2) Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend- LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <4us, L1 <32us ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp- LnkCtl: ASPM L1 Enabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- DevCap2: Completion Timeout: Range B, TimeoutDis+, LTR+, OBFF Via WAKE# DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF Disabled LnkCtl2: Target Link Speed: 2.5GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP+ BadDLLP- Rollover- Timeout- NonFatalErr + CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr + AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn- Capabilities: [140 v1] Device Serial Number 7c-7a-91-ff-ff-3d-27-91 Capabilities: [14c v1] Latency Tolerance Reporting Max snoop latency: 3145728ns Max no snoop latency: 3145728ns Capabilities: [154 v1] Vendor Specific Information: ID=cafe Rev=1 Len=014 <?> Kernel driver in use: iwlwifi Kernel modules: iwlwifi

5 years, 4 months

[opensuse-factory] TW 64 bit glibc-32bit lags behind glibc

by Andrei Borzenkov

glibc is 2.22-8.2 while glibc-32bit is 2.22-7.1. I thought they are built from the same source - how can versions be different? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

[opensuse-factory] Legacy tray icons on Plasma Workspace 5.5.4

by Bjoern Voigt

Could someone confirm, that legacy tray icons do not work as expected in Tumbleweed with KDE Plasma desktop? (Support for legacy tray icons is restored in KDE Workspace 5.4 or 5.5.) At first I saw this issue using Pidgin 3.0.0 (GTK+3, Pidgin development version). The tray icon is displayed very small and the context menu does not work. Pidgin is difficult to compile. So I searched a small example, which is easy to test: Here is a Java tray icon demo: https://docs.oracle.com/javase/tutorial/uiswing/examples/misc/index.html#Tr… Setup: * download and unpack the ZIP file * change Windows LaF to Metal LaF. The metal LaF is already there as a comment: //UIManager.setLookAndFeel("com.sun.java.swing.plaf.windows.WindowsLookAndFeel"); UIManager.setLookAndFeel("javax.swing.plaf.metal.MetalLookAndFeel"); * compile and run the demo: "ant run" or "ant run; ant jar && java -jar dist/TrayIconDemo.jar" The icon is displayed correctly. But the context menu does not work. My setup (standard Tumbleweed - openSUSE Tumbleweed (20160228) (x86_64)): * Plasma Workspace 5.5.1 * Plasma Framework 5.19.0 * Qt 5.5.1 /usr/bin/xembedsniproxy (from plasma5-workspace) shows messages like these: kde.xembedsniproxy: trying to dock window 130023428 kde.xembedsniproxy: adding damage watch for 130023428 kde.xembedsniproxy: Skip transparent xembed icon for 130023428 "JavaEmbeddedFrame" kde.xembedsniproxy: No xembed icon for 130023428 "JavaEmbeddedFrame" kde.xembedsniproxy: Skip transparent xembed icon for 130023428 "JavaEmbeddedFrame" kde.xembedsniproxy: No xembed icon for 130023428 "JavaEmbeddedFrame" kde.xembedsniproxy: Skip transparent xembed icon for 130023428 "JavaEmbeddedFrame" kde.xembedsniproxy: No xembed icon for 130023428 "JavaEmbeddedFrame" kde.xembedsniproxy: Scaling pixmap of window 130023428 "JavaEmbeddedFrame" from w*h 24 24 kde.xembedsniproxy: Scaling pixmap of window 130023428 "JavaEmbeddedFrame" from w*h 24 24 kde.xembedsniproxy: Scaling pixmap of window 130023428 "JavaEmbeddedFrame" from w*h 24 24 kde.xembedsniproxy: Received click 3 with passed x*y 1635 1050 kde.xembedsniproxy: Received click 3 with passed x*y 1635 1050 Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

[opensuse-factory] openSUSE Tumbleweed - Review of the weeks 2016/6 & 7

by Dominique Leuenberger / DimStar

Dear Tumbleweed users and hackers, Again I cover two weeks, with the 2nd one being more of troubles than releases. The snapshots covered this week are 0205, 0207, 0208, 0209 (week 6) and 0212 (week 7). I’ll try to explain at the end what was holding us back in week 7. Noteworthy updates as part of the last snapshots: * AppStream-glib update. Most notably: the icons are no longer duplicated across multiple repositories metadata * GCC 5.3.1 is now the default compiler * Mozilla Firefox 44 * cmake 3.4.3 – most importantly, ‘modules’ no longer get a soname during linking. Some packages might fail rpmlint now in case the shared library packaging policy was not applied * GStreamer 1.6.3 – Many bugfixes * Plasma 5.5.4 – you know you want it! What is brewing in the next snapshot (0217+) * Firewalld – available for testers. A future version should bring migration assistance from SUSEFirewall2 to firewalld * plymouth gained a new plugin to show simple texts (used to indicate which partition to unlock) I would like to introduce a new section, mentioning ‘bugs I feel are noteworthy’. The list is incomplete and might not cover the bug YOU had seen, and it shall not be a complete list of new bugs reported. * Tumbleweed users using LUKS encrypted devices reported plymouth related issues. Current workaround identified is to disable plymouth at boot time with “plymouth.enable=0″ on kernel command line. boo#966255 * systemd 228 introduced cgroup Task accounting to limit fork bombs and the like. it seems a user logging in on the terminal is more limited than a GUI user, which could result in the system running out of resources to fork more tasks. boo#966878 And, last but not least, as promised, a word about why there have been no new snapshots released since 0209 (released on Feb 12): openSUSE Tumbleweed relies heavily on openQA and the test results we receive from the automated tests. For not yet clear reasons, the most powerful worker we have (had) on openQA.opensuse.org decided to quit its job (it did not mention the wish to find a new career path). This left openQA running with only 2 workers left instead of the usual 10. The remaining work force is largely overloaded and can’t cope with the workload. There were only two options left for us: release without testing or hold back the snapshots. As evidence shows, we opted to hold back the snapshots. Various solutions are currently evaluated to get new worker power on openQA, which includes borrowing machines from other SUSE owned instances. Have a great weekend ahead, Dominique -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

[opensuse-factory] New package: Ardour

by Roman Evstifeev

Hi. I am trying to get Ardour package to the Factory. Ardour is software hard-disk-recorder and digital-audio-workstation. It is avilable under GPLv2 from its website http://ardour.org and actively developed on github https://github.com/Ardour/ardour I will try to maintain it in the multimedia:apps repository -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory February 2016