July 2015 - 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] openSUSE maintainer finder tool
by Bernhard M. Wiedemann 14 Jan '16

14 Jan '16

Hi, during our Hackweek at SUSE I spent a day or two to improve my tool to help finding the maintainer for software in Factory, which comes in handy for bugzilla-screening (getting bugs to the right people). You can use the tool at http://maintainer.zq1.de/ You can give it command names, full filepath, or package names (exact matches (including case) only) If you want to run or extend it, the code is all open on https://github.com/bmwiedemann/susepkginfo and the databases can be fetched from http://aw.zq1.de/db.suse/ The actual maintainer information comes from OBS, so is always current. Ciao Bernhard M. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

11 14

[opensuse-factory] xgettext aborts [Fwd: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64]
by Bernhard Voelker 30 Nov '15

30 Nov '15

What happened to xgettext? [ 198s] /usr/bin/xgettext --default-domain=coreutils --directory=.. \ [ 198s] --add-comments=TRANSLATORS: --keyword=_ --keyword=N_ --flag=_:1:pass-c-format --flag=N_:1:pass-c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --flag=asnprintf:3:c-f ormat --flag=asprintf:2:c-format --flag=error:3:c-format --flag=error_at_line:5:c-format --flag=vasnprintf:3:c-format --flag=vasprintf:2:c-format --flag=verror:3:c-format --flag=verror_at_line:5:c- format --flag=wrapf:1:c-format --flag=xasprintf:1:c-format --flag=xfprintf:2:c-format --flag=xprintf:1:c-format --from-code=UTF-8 --keyword=proper_name:1,'"This is a proper name. See the gettext ma nual, section Names."' --keyword=proper_name_utf8:1,'"This is a proper name. See the gettext manual, section Names."' ${end_of_xgettext_options+} --flag=error:3:c-format --flag=error_at_line:5:c-f ormat --keyword='proper_name:1,"This is a proper name. See the gettext manual, section Names."' --keyword='proper_name_utf8:1,"This is a proper name. See the gettext manual, section Names."' --flag =asprintf:2:c-format --flag=vasprintf:2:c-format --flag=verror:3:c-format --flag=verror_at_line:5:c-format --flag=xprintf:1:c-format --flag=xvprintf:1:c-format --flag=xfprintf:2:c-format --flag=xvf printf:2:c-format --flag=xasprintf:1:c-format \ [ 198s] --files-from=./POTFILES.in \ [ 198s] --copyright-holder='Free Software Foundation, Inc.' \ [ 198s] --package-name="${package_gnu}coreutils" \ [ 198s] --package-version='8.22' \ [ 198s] --msgid-bugs-address="$msgid_bugs_address" \ [ 198s] ;; \ [ 198s] esac [ 198s] *** Error in `/usr/bin/xgettext': realloc(): invalid pointer: 0x00000000018ff590 *** [ 198s] ======= Backtrace: ========= [ 198s] /lib64/libc.so.6(+0x7343f)[0x7fa6640e043f] [ 198s] /lib64/libc.so.6(+0x78cae)[0x7fa6640e5cae] [ 198s] /lib64/libc.so.6(+0x7bde5)[0x7fa6640e8de5] [ 198s] /usr/lib64/libgettextlib-0.19.1.so(xrealloc+0xe)[0x7fa66445b56e] [ 198s] /usr/bin/xgettext[0x40b301] [ 198s] /usr/bin/xgettext[0x40b38d] [ 198s] /usr/bin/xgettext[0x40b4e1] [ 198s] /usr/bin/xgettext[0x40b98e] [ 198s] /usr/bin/xgettext[0x40ba93] [ 198s] /usr/bin/xgettext[0x40c340] [ 198s] /usr/bin/xgettext[0x406953] [ 198s] /usr/bin/xgettext[0x4052cc] [ 198s] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fa66408eb05] [ 198s] /usr/bin/xgettext[0x405ba3] Have a nice day, Berny -------- Original Message -------- Subject: Build failure of Base:System/coreutils-testsuite openSUSE_Factory/x86_64 Date: Wed, 11 Jun 2014 18:15:31 +0000 From: hermes(a)opensuse.org Reply-To: hermes(a)opensuse.org To: mail(a)bernhard-voelker.de Package coreutils-testsuite (version 8.22-248.68) of project Base:System failed to build for openSUSE_Factory / x86_64. Review the build log: osc remotebuildlog Base:System coreutils-testsuite openSUSE_Factory x86_64 | less Check out the package for editing: osc checkout Base:System coreutils-testsuite -- Hermes messaging (http://hermes.opensuse.org) openSUSE Build Service (https://build.opensuse.org/) -- 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] KF5: kdevelop is missing drkonqi
by Hartmut Rosch 29 Oct '15

29 Oct '15

Hello, I just updated from rev. 13.2 to tumbleweed. It doesn't work as I expected but with plasma5 it should show differences. For my more or less privete developing work i am using kdevelop quite often. And with KDE4 it worked well. Now after the upgrade to tumbleweed it crashes when kdevelp is calling drkonqi. It looks like that kdevelop is calling kdeinit and after that drkonqi fails to start. I am attaching a crash.txt which reports the crash -- greetings Hartmut Rosch Delmenhorst -----------

3 3

[opensuse-factory] Tumbleweed - Review of the week (2015/18)
by Dominique Leuenberger / DimStar 28 Oct '15

28 Oct '15

Dear Tumbleweed users and hackers, In good tradition I am pleased to also give you an overview of the last week on what happened in Tumbleweed. We had 'only' two snapshots released this week (0425 & 0430). The main reason was that the update of parted to version 3.2 managed to sneak through the staging area, yet had a negative impact on the full post -integration test runs (resizing partitions while installing openSUSE side-by-side of Windows is not properly handled). So, parted 3.2 is currently taken out of Tumbleweed again - but of course scheduled to reach you later: once YaST has been adjusted to handle the changes. On the side of things that DID happen: * As discussed on the -factory mailinglist, a couple packages have been converted from GStreamer 0.10 to 1.0 (banshee, gnac) * The kernel has been updated to version 4.0 What can we expect in the upcoming period? * The KDE Team is hard at work to make Plasma 5.3 the default for openSUSE. Work is still going on, but the staging areas are looking promising already. * The switch of GCC 5 as default version is also still work in progress. This is not forgotten yet. * Progress on Ruby 2.2 seems to have stalled - there hasn't been any progress in a while now. Volunteers to step up and work on the fallouts in Staging:H are welcome [0] [0] https://build.opensuse.org/project/show/openSUSE:Factory:Staging:H -- Have a lot of fun, Dimstar / Dominique Leuenberger <dimstar(a)opensuse.org> -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

23 73

Re: [opensuse-factory] A users wishlist to make zypper up/dup & suse noob-friendly
by Thomas Langkamp 28 Oct '15

28 Oct '15

> snip > > > IMO, Tumbleweed is for experts :-) > > - -- > Cheers / Saludos, > > Carlos E. R. > > No it's not. I'm running it successfully and am far from an expert. > Yes. It's for experienced users > snip > > Steven Thank you very much Carlos, Dimstar, Dsant, Jim, Jimmy, Ken, Lars, Richard, Roman, Steven for your inputs. Summary ########## The above is valid: TW in its current form is for experts / experienced users / users following this list. That is exactly why I started this discussion: subject: "A users wishlist to make zypper up/dup & suse noob-friendly" See? I said implicitly that zypper is too complicated and my wish is, that it - or another update mechanism - would make TW beginner-friendly. And most of the improvements could also work for Leap, but that would be a side-effect. Results ########### a) on installation user opt-in to packman-repo => legaly not possible, however one suggestion was not yet commented: "There could be a supplementary screen : * If you live in US click here (open-sources repositories, DMCA ok...). * If you live in UK/Germany/Europe... click here (Packman repository added) [...] Dsant" b) default to packman priority 98 & auto vendor change => implementation possible through .repo parameter priority, but concerns about a race of lowest priorities & untested packages & not needing the whole repo. => solutions: - the noob does not know which subset of packman he needs to get multimedia working, thus just do the vendor change per default. - implement openQA also for packman to test & thus to allow automatical vendor change for this one repo only. - there is no race for lowest priority if only one repo==packman gets the 98 priority as the default. Can we agree that packman is the most important user repo of openSUSE so that it should be treated special? c) after adding packman do auto zypper dup or up with vendor change once: PackageKit / Apper cannot handle conflicts and thus is not supported in TW. => solutions: 1) enhance Apper to handle conflicts 2) automatizing zypper: noobs cannot use cron, nor command line / yast-gui, nor can they decide between "no / vendor change", "up / dup" => further comments: A users confirmation to install the automatically proposed update is desired, agreed. A password will be needed for new software only, as this is already the way PackageKit/Apper & Win7 (just tested) are doing it from user accounts. d) install recommends only once during installation as default, so that uninstalled apps do not come back => so far +1 for this e) I would update the whole wiki with the changes Thank you, thomas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

10 31

[opensuse-factory] Application:Geo status
by Angelos Tzotsos 26 Sep '15

26 Sep '15

Hi all, Since there is no Geo specific mailing list, I decided to bring some issues to the factory list: 1. GRASS 7 has been released some time now. We are still maintaining 2 versions in Geo repository: grass (6.4.x) and grass7 (7.x). I think we need to merge grass7 into grass package. The question is: should we create a grass6 package for 6.x users? I am sure those users exist out there... 2. PostGIS 2 is out for quite a long time. We have postgis and postgis2 packages in our repository. postgis is disabled and all binaries are wiped out for some time now (since we removed RedHat based repositories). Question: should we merge postgis2 to postgis? and drop postgis2 package? 3. openSUSE 42 has been added to the Geo project. There are some dependencies missing, but things look good in general. Should we add the needed packages in Geo repository or submit the needed packages to 42? 4. QGIS 2 is out for at least 2 years. There is no point to keep qgis and qgis2 packages anymore. Otto has proposed to have qgis package (latest stable release - 2.10.1), qgis-master (nightly build from git, as we already have) and qgis-ltr (Long Time Supported Release - 2.8.3). I agree to drop QGIS 1.x package. 5. Several Geo packages are now in Factory so we should be very careful with what is enabled to build in Geo repository. Those packages should be used from the upstream openSUSE release (eg. geos, hdf5, proj). I made some adjustments to fix this issue. 6. GDAL made it to Factory but was never released as part of a stable openSUSE release (it would be released in 13.3, so we need to submit it to 42). Also GDAL 2.0 was released some days ago. I am sure that most downstream projects are not ready for the switch. Should we create a gdal2 package or just wait a few months? Best, Angelos -- Angelos Tzotsos, PhD OSGeo Charter Member http://users.ntua.gr/tzotsos -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

5 7

[opensuse-factory] No Activities, was: KDE Virtual desktops all identical
by Patrick Shanahan 17 Sep '15

17 Sep '15

* Stefan Bruens <stefan.bruens(a)rwth-aachen.de> [07-30-15 23:00]: [...] > Thats kind of usage is exactly what activities are meant for. > > Virtual desktops are orthogonal to activies, although virtual desktops have > been abused for this kind of usage. > > Virtual desktops provide exactly one thing, more space, nothing else. > > There is one thing current activities lack, an advanced/configurable > switcher/overview, but thats it. I have a thread in opensuse-kde discussing the lack of activities or any method of creating an activity on my Tw systems, also another server on 13.1. I have the activities widget but nothing happens when trying to activitate it. The "Desktop" menu does not provide for "creating" an activity. And I have three other Tw systems which also have no provision for "creating" an activity. wtf? Any help appreciated. (About to file bugs at kde and openSUSE). -- (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

3 26

[opensuse-factory] Distortet or even black screen after resuming from hibernation
by mh＠mike.franken.de 06 Aug '15

06 Aug '15

Hi *, I didn't get any reaction on this question, yet, so I try it again :) Sorry for that, but hibernating/resuming is an essential feature for me. >Changed packages: >==== Mesa ==== >Version update (10.5.7 -> 10.6.1) >Subpackages: Mesa-32bit Mesa-devel Mesa-dri-devel Mesa-libEGL-devel >Mesa-libEGL1 Mesa-libEGL1-32bit Mesa-libGL-devel Mesa-libGL1 >Mesa-libGL1-32bit Mesa-libGLESv1_CM-devel Mesa-libGLESv1_CM1 Mesa-libGLESv2-2 >Mesa-libGLESv2-devel Mesa-libglapi-devel Mesa-libglapi0 Mesa-libglapi0-32bit >libOSMesa-devel libOSMesa9 libOSMesa9-32bit libgbm-devel libgbm1 >libgbm1-32bit libvdpau_nouveau libvdpau_r300 libvdpau_r600 libvdpau_radeonsi >libwayland-egl-devel libwayland-egl1 libxatracker2 >- adjust libdrm dependencies >- Update to version 10.6.1 > * This release includes core mesa and glsl patches (amonst which > a Dota2 Reborn bugfix) affecting all dri drivers, nouveau specific Are there any known problems with these nouveau patches and some NVidia cards? My card: 01:00.0 VGA compatible controller: NVIDIA Corporation GT218 [GeForce 210] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. Device 2177 Flags: bus master, fast devsel, latency 0, IRQ 28 Memory at f6000000 (32-bit, non-prefetchable) [size=16M] Memory at e0000000 (64-bit, prefetchable) [size=256M] Memory at f0000000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [size=128] Expansion ROM at f7000000 [disabled] [size=512K] Capabilities: [60] Power Management version 3 Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [78] Express Endpoint, MSI 00 Capabilities: [b4] Vendor Specific Information: Len=14 <?> Capabilities: [100] Virtual Channel Capabilities: [128] Power Budgeting <?> Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024 <?> Kernel driver in use: nouveau Kernel modules: nouveau After resuming from hibernation, I see a distortet or even black screen. Never observed this before. In the log I get: [...] kernel: nouveau [ VOLT][0000:01:00.0] GPU voltage: 900000uv kernel: nouveau [ PTHERM][0000:01:00.0] fan management: automatic kernel: nouveau [ CLK][0000:01:00.0] --: core 405 MHz shader 810 MHz memory 405 MHz kernel: nouveau [ DRM] resuming client object trees... kernel: nouveau [ DRM] resuming display... kernel: nouveau [ DRM] resuming console... [...] kernel: nouveau E[plasmashell[2264]] fail set_domain kernel: nouveau E[plasmashell[2264]] validating bo list kernel: nouveau E[plasmashell[2264]] validate: -22 kernel: nouveau E[plasmashell[2264]] fail set_domain kernel: nouveau E[plasmashell[2264]] validating bo list kernel: nouveau E[plasmashell[2264]] validate: -22 kernel: nouveau E[ PGR][0000:01:00.0] magic set 0: kernel: nouveau E[ PGR][0000:01:00.0] 0x00408604: 0x2008180f kernel: nouveau E[ PGR][0000:01:00.0] 0x00408608: 0x0005fa20 kernel: nouveau E[ PGR][0000:01:00.0] 0x0040860c: 0x40000432 kernel: nouveau E[ PGR][0000:01:00.0] 0x00408610: 0x3ce00000 kernel: nouveau E[ PGR][0000:01:00.0] TRAP_TEXTURE - TP0: LINEAR_MISMATCH kernel: nouveau E[ PGR][0000:01:00.0] ch 9 [0x003f518000 plasmashell[2264]] subc 3 class 0x8597 mthd 0x0f04 data 0x3f800000 kernel: nouveau E[ PFB][0000:01:00.0] trapped read at 0x00203f3000 on channel 0x0003f518 [plasmashell[2264]] PGRAPH/TEXTURE/00 reason: PAGE_NOT_PRESENT kernel: nouveau E[ PGR][0000:01:00.0] magic set 0: kernel: nouveau E[ PGR][0000:01:00.0] 0x00408604: 0x2008140f kernel: nouveau E[ PGR][0000:01:00.0] 0x00408608: 0x00204f70 kernel: nouveau E[ PGR][0000:01:00.0] 0x0040860c: 0x40000432 kernel: nouveau E[ PGR][0000:01:00.0] 0x00408610: 0x4f700000 kernel: nouveau E[ PGR][0000:01:00.0] TRAP_TEXTURE - TP0: FAULT kernel: nouveau E[ PGR][0000:01:00.0] ch 9 [0x003f518000 plasmashell[2264]] subc 3 class 0x8597 mthd 0x108c data 0x204faaf3 kernel: nouveau E[ PFB][0000:01:00.0] trapped read at 0x002041f000 on channel 0x0003f518 [plasmashell[2264]] PGRAPH/TEXTURE/00 reason: PAGE_NOT_PRESENT kernel: nouveau E[ PGR][0000:01:00.0] magic set 0: kernel: nouveau E[ PGR][0000:01:00.0] 0x00408604: 0x20094705 kernel: nouveau E[ PGR][0000:01:00.0] 0x00408608: 0x002041f0 kernel: nouveau E[ PGR][0000:01:00.0] 0x0040860c: 0x40000432 kernel: nouveau E[ PGR][0000:01:00.0] 0x00408610: 0x41f00000 kernel: nouveau E[ PGR][0000:01:00.0] TRAP_TEXTURE - TP0: FAULT kernel: nouveau E[ PGR][0000:01:00.0] ch 9 [0x003f518000 plasmashell[2264]] subc 3 class 0x8597 mthd 0x0f04 data 0xbaf9a934 kernel: nouveau E[ PGR][0000:01:00.0] magic set 0: kernel: nouveau E[ PGR][0000:01:00.0] 0x00408604: 0x20087e0f kernel: nouveau E[ PGR][0000:01:00.0] 0x00408608: 0x00205981 kernel: nouveau E[ PGR][0000:01:00.0] 0x0040860c: 0x40000432 kernel: nouveau E[ PGR][0000:01:00.0] 0x00408610: 0x59500000 kernel: nouveau E[ PGR][0000:01:00.0] TRAP_TEXTURE - TP0: FAULT kernel: nouveau E[ PGR][0000:01:00.0] ch 9 [0x003f518000 plasmashell[2264]] subc 3 class 0x8597 mthd 0x1b0c data 0x1000f010 kernel: nouveau E[ PFB][0000:01:00.0] trapped read at 0x0020598100 on channel 0x0003f518 [plasmashell[2264]] PGRAPH/TEXTURE/00 reason: PAGE_NOT_PRESENT kernel: nouveau E[ PGR][0000:01:00.0] magic set 0: kernel: nouveau E[ PGR][0000:01:00.0] 0x00408604: 0x2008530a kernel: nouveau E[ PGR][0000:01:00.0] 0x00408608: 0x00204f68 kernel: nouveau E[ PGR][0000:01:00.0] 0x0040860c: 0x40000432 kernel: nouveau E[ PGR][0000:01:00.0] 0x00408610: 0x4f200000 kernel: nouveau E[ PGR][0000:01:00.0] TRAP_TEXTURE - TP0: FAULT kernel: nouveau E[ PGR][0000:01:00.0] ch 9 [0x003f518000 plasmashell[2264]] subc 3 class 0x8597 mthd 0x1b0c data 0x1000f010 [...] This happens with kernel 4.0.5-3 and also with 4.0.5-1! Any idea? Thx! Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

7 22

[opensuse-factory] snapperd
by ianseeks 06 Aug '15

06 Aug '15

hi I understand that "snapperd" is only for btrfs but its launched daily and hourly by cron even though i don't use btrfs. If this a failure of the installation process that adds these cron jobs? (i also have the bluetooth service automatically started even though i do not have any bluetooth system on my machine - i think i've dealt with that via kcm-systemd) Do we have a Plasma tool to manage crontab (there used to be a kcron if i remember correctly) ? regards Ian -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 15