LinuxQuestions.org - [SOLVED] Requests for -current (20151216)

Page 1 of 69

Show 50 post(s) from this thread on one page

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Requests for -current (20151216) (https://www.linuxquestions.org/questions/slackware-14/requests-for-current-20151216-a-4175561577/)

rworkman

12-16-2015 12:18 AM

Requests for -current (20151216)

First of all, this does not mean that a release is imminent - like many of you, I definitely think that -current is shaping up quite nicely right now and is getting close to release quality, but of course, that's not my decision (and I can always find "just one more thing" to add/upgrade/whatever) :-)

I've already got these queued up for consideration:

* bluez-5.x, sbc, blueman-2.0.x, Cython (build dep for blueman)

* polkit-0.113 and polkit-gnome-0.105 -- these are quite different and thus may not make the cut. They're working well here but it wouldn't hurt to get some more testing; if anyone's interested, mail me and I'll provide links.

* upower 0.99.3 ?? This has a minor (IMHO) regression with respect to 0.9.23, but we would get a maintained version instead of an abandoned-by-upstream branch. The regression is basically this: upower-0.9.23 advised whether suspend/hibernate was possible itself, i.e. apps like xfce4-power-manager asked upower if it was possible and then invoked the suspend/hibernate by some means (in the case of xfpm, via pm-(suspend|hibernate)). That ability was removed from upower, so now ConsoleKit2 handles that side of things. However, CK2 only implemented a check for whether the hardware is *capable* of suspend/hibernate, which means that there is *not* a check for whether hibernate is actually *possible* - i.e. is there enough swap space available? The result is that in e.g. xfce, the hibernate option is always present in the logout dialog if the system is capable of hibernating, even though the system may not have enough swap space to do so (in my case, there is zero swap space). Is this a sufficient regression to avoid upower-0.99.3? Alternatively, does someone with more time want to grab the code from upower-0.99.3 and make whatever changes are needed to merge it into upstream CK2 (assuming license compatibility) and do a pull request with them? I glanced over it, and it looks relatively trivial to do for someone competent (I think even I can do it, so competence isn't necessarily a requirement ;-) - I just don't have time at the moment). If so, there's already an open issue there on the CK2 github page - just reference that in your PR. I'll be happy to test and add a Signed-Off-By on the PR if you'd like.
EDIT: upower-0.99.3 is out of the running for this cycle - it's fine with xfce, but kde is not. Maybe next time. :-)

pprkut has these things queued up already:
* iftop libevent libodfgen mpg123 sqlite taglib wavpack

We already know that PAM is desired by some and not by others. This is not a place to discuss it or give pros/cons of either, as those are pretty much known too. Whether it's ever been or is currently under consideration is not my place to say, but I will point out that every time there's a new flame fest about it, none of us want to touch it again for a while. Let that be a point of education.

rworkman

12-16-2015 12:58 AM

Dammit. I broke slackpkg. Until Pat gets a fix out, here it is:
Open /usr/libexec/slackpkg/core-functions.sh
Go to line #282
You should see this:

Code:

to the closest mirror and is very slow.\n\"

Make it this:

Code:

to the closest mirror and is very slow.\n"

Sincerest apologies for not keeping the stuff in my pending tree in sync with the stuff on my testing system. :(

EDIT: Fixed now; hopefully nobody even got a broken package :-)

a4z	12-16-2015 02:39 AM

I have a question, to the new gcc5.3
there was an ABI change in libstdc++, and the new ABI should be default on, except it was changed.
so I would expect to see more packages rebuilded.
Or is it turned off? This would be not so cool because that would mean that shipped C++ library is not ISO standard compatible, that's why sting and list where changed.
and will be incompatible with the rest of the world because I expect the rest of the world to switch to ISO standard implementation as soon as it is default from the compiler, which is with gcc5.3

e5150

12-16-2015 02:45 AM

I would like to see the certwatch cronjob in openssl patched, as it stands it does basically nothing, as it only looks for regular files in /etc/ssl/certs, while the directory is populated by symlinks to /usr/share/ca-certificates.

Code:

--- certwatch.new      2015-12-02 23:02:37.000000000 +0100

+++ certwatch  2015-12-12 23:57:11.566226350 +0100

@@ -83,8 +83,9 @@

  fi

 done



-find $CERTDIR -type f -maxdepth 1 | while read certfile ; do

-  if [ "$certfile" != "/etc/ssl/certs/ca-certificates.crt" ]; then

+find $CERTDIR \( -type f -o -type l \) -maxdepth 1 | while read certfile ; do

+  if [ "$certfile" != "$CERTDIR/ca-certificates.crt" ]; then

+  certfile="$(realpath "$certfile")"

  certfilebase="$(basename "$certfile")"

  inform=PEM

  echo "$certfile" | grep -q -i '\.net$'

ReaperX7

12-16-2015 03:51 AM

Robby, avoid upower-0.99.3. It breaks the desktop completely last I tried it. Icons literally were a mess. It's built solely for systemd-logind usage. The real problem is pm-utils. The pm-utils, upower, and xfce4-power-manager all have some cyclical dependencies so you have to rebuild each package a few times to match the dependencies correctly. The problem is, if pm-utils isn't dependency matched to upower and xfce4-power-manager isn't built for upower and pm-utils, it tends to start misbehaving.

This is actually a package I've had to rebuild even in 14.1 because it was targeting an older dependency library.

Upower-0.9.23 should work fine with sysvinit utility based or derived without issue.

gmgf	12-16-2015 04:07 AM

xfce4-power-manager (1.5 version) support Upower-0.9.23

http://archive.xfce.org/src/xfce/xfc...r-manager/1.5/

it compil perfectly, but i don't have laptop, for testing correctly.

gmgf	12-16-2015 06:12 AM

Oops sorry ;)

xfce4-power-manager (1.5 version) support Upower-0.99.3

http://archive.xfce.org/src/xfce/xfc...r-manager/1.5/

it compil perfectly, but i don't have laptop, for testing correctly.

Raveriux

12-16-2015 09:11 AM

I still suggest support out of the box for old music tracker files including libmodplug and rebuilding audaciuous-plugins against it. Someone also mentioned gstreamer rebuild agains libmodplug for the same reason.

Nille_kungen

12-16-2015 10:03 AM

Since the old thread is locked i will repost here.
sunet.se mirrors should be removed from /etc/slackpkg/mirrors since they don't host linux distributions any more and the links are dead.
http://www.linuxquestions.org/questi...4/#post5426031
http://www.linuxquestions.org/questi...ml#post5456931

dugan

12-16-2015 10:29 AM

I will ask for it again: FluidSynth added, and SDL_mixer rebuilt against it.

ivandi

12-16-2015 11:06 AM

rc.cgmanager

Quote:

a/sysvinit-scripts-2.0-noarch-25.txz: Rebuilt.

rc.S: If executable, start rc.cgmanager.
rc.6: If executable, stop rc.cgmanager.

Running cgmanager from rc.S doesn't make sense to me. Switching to runlevel 1 will kill it and switching back to runlevel 3 won't start it. It is a d-bus controlled daemon and should be run in rc.M after rc.messagebus.

Cheers

rworkman

12-16-2015 11:21 AM

Quote:

Originally Posted by ReaperX7 (Post 5464971)

Robby, avoid upower-0.99.3. It breaks the desktop completely last I tried it. Icons literally were a mess.

That's a local system issue caused by not recompiling something, most likely xfce4-settings.

Quote:

It's built solely for systemd-logind usage. The real problem is pm-utils.

Nope. pm-utils is just a set of scripts, and they do what they do regardless of upower.

Quote:

The pm-utils, upower, and xfce4-power-manager all have some cyclical dependencies so you have to rebuild each package a few times to match the dependencies correctly. The problem is, if pm-utils isn't dependency matched to upower and xfce4-power-manager isn't built for upower and pm-utils, it tends to start misbehaving.

There is at least one, and maybe two, actual problem(s) with upower-0.99.3. The handwaving above is not one of them.

Quote:

This is actually a package I've had to rebuild even in 14.1 because it was targeting an older dependency library.

I don't understand the expectation here - my (realistic IMHO) expectation is that recompiles will be needed. Why would you expect otherwise?

Quote:

Upower-0.9.23 should work fine with sysvinit utility based or derived without issue.

Agreed, but that's not the issue. It also has at least one bug here that is a showstopper for me (and will be for others who depend on that particular feature), and while I've managed to backport a patch from master to fix one of the bugs, at least one remains. More importantly, the 0.9.23 branch is simply not maintained, so fixes to things like blacklisting hid devices and enhancing support for multiple batteries won't make it there (and backporting multiple battery support is not trivial - I tried).

rworkman

12-16-2015 11:27 AM

Quote:

Originally Posted by ivandi (Post 5465121)

Running cgmanager from rc.S doesn't make sense to me.

The lxc guys (cgmanager devs) suggested that it should be started when the cgroups stuff is set up, which is done in rc.S, so that's why it was started there.

Quote:

Switching to runlevel 1 will kill it and switching back to runlevel 3 won't start it.

That's a valid point...

andrew.46

12-16-2015 03:33 PM

After a few minutes of play there is now a politely worded 'nag' screen for the electricsheep screensaver, top left corner:

Code:

please update to latest client from www.electricsheep.org

Currently (sic) we have v2.7b11 while v2.7b33 is available online. I confess I have not yet investigated the newer version...

_gin	12-16-2015 05:41 PM

Nice upgrades from changelog "Wed Dec 16 04:21:07 UTC 2015", thank you.

Can you upgrade these softwares as well?

at 3.1.12 --> 3.1.16
diffstat 1.53 --> 1.60
enscript 1.6.5.2 --> 1.6.6
joe 3.7 --> 4.1
lsof 4.83 --> 4.89
rpm 4.10.0 --> 4.12.0.1
soma 2.8.5 --> 2.10.4
sysstat 9.0.6.1 --> 11.0.8

http://anonscm.debian.org/cgit/collab-maint/at.git
ftp://invisible-island.net/diffstat
http://ftp.gnu.org/gnu/enscript
http://sourceforge.net/projects/joe-editor
ftp://sunsite.ualberta.ca/pub/Mirror/lsof
http://rpm.org
http://dawoodfall.net/slackbuilds/noversion/soma
http://sebastien.godard.pagesperso-orange.fr (sysstat)

ReaperX7

12-16-2015 06:55 PM

Quote:

Originally Posted by rworkman (Post 5465127)

That's a local system issue caused by not recompiling something, most likely xfce4-settings.

Nope. pm-utils is just a set of scripts, and they do what they do regardless of upower.

There is at least one, and maybe two, actual problem(s) with upower-0.99.3. The handwaving above is not one of them.

I don't understand the expectation here - my (realistic IMHO) expectation is that recompiles will be needed. Why would you expect otherwise?

Agreed, but that's not the issue. It also has at least one bug here that is a showstopper for me (and will be for others who depend on that particular feature), and while I've managed to backport a patch from master to fix one of the bugs, at least one remains. More importantly, the 0.9.23 branch is simply not maintained, so fixes to things like blacklisting hid devices and enhancing support for multiple batteries won't make it there (and backporting multiple battery support is not trivial - I tried).

Well, if it can be done, then we should try at least. I don't think I rebuilt xfce4-settings last time, but I can try and give it a heave-ho on my test system and see what happens. However, I am expecting problems like always with it, but I will report back what I get.

I am however going to report one thing:

upower-0.9.23 does this currently when ran with upower -w

Code:

bash-4.3# upower -w



(upower:2502): libupower-glib-WARNING **: Couldn't get total: cannot enable timerstats

Total wakeups per minute: 0

After I rebuild it:

Code:

bash-4.3# upower -w



(upower:11111): libupower-glib-WARNING **: Couldn't get total: cannot enable timerstats

Total wakeups per minute: 0

Wakeup sources:

userspace:0 id:0, interrupts:2147483648.0, cmdline:interrupt, details:timer

userspace:0 id:4082, interrupts:0.5, cmdline:kernel-ipi, details:Rescheduling interrupts

Not sure why I'm getting more output...

By the way is CONFIG_TIMER_STATS enabled in the kernel?

You mentioned the missing functionality. Well, in any case, if functionality is needed then yes, it is needed and the code needs to be patched in and the pull request made for CK2.

willysr

12-16-2015 10:53 PM

Few updates:
Subversion 1.9.3
Samba 4.3.3
Ruby 2.2.4
Kdelibs 4.14.15
Httpd 2.4.18
Perl 5.22.1

gmgf	12-17-2015 02:09 AM

Another, ModemManager-1.4.12

http://www.freedesktop.org/software/...-1.4.12.tar.xz

gmgf	12-17-2015 02:30 AM

Maybe python-setuptools-19.1.1 also

https://pypi.python.org/pypi/setuptools

gmgf	12-17-2015 03:29 AM

For upower, maybe manjaro upower-pm-utils patch can be useful, just suggestion ;)

https://github.com/manjaro/packages-...power-pm-utils

ReaperX7

12-17-2015 04:20 AM

Thanks gmgf, I'll test these.

Okay, we will need CONFIG_TIMER_STATS in the kernel for upower. Slackware doesn't ship it enabled.

Kernel Hacking >[*] Kernel Debugging >[*] Collect Kernel Timers Statistics

Upower uses this to check for information on processor wakeups. Looks like I'm building a test kernel too. Will report back later.

Edit:

Rebuilt kernel with timer statstics and upower with Manjaro patches.

Results from upower -w:

Code:

bash-4.3# upower -w

Total wakeups per minute: 584

Wakeup sources:

userspace:0 id:4082, interrupts:212.0, cmdline:kernel-ipi, details:Rescheduling interrupts

userspace:0 id:4081, interrupts:109.5, cmdline:kernel-ipi, details:Local timer interrupts

userspace:0 id:35, interrupts:81.0, cmdline:interrupt, details:PCI-MSI-edge      nvkm

userspace:0 id:18, interrupts:55.5, cmdline:interrupt, details:IO-APIC  18-fasteoi  ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7

userspace:0 id:7, interrupts:49.0, cmdline:interrupt, details:

userspace:1 id:2285, interrupts:23.3, cmdline:/usr/bin/firefox, details:hrtimer_start_range_ns (hrtimer_wakeup)

userspace:0 id:19, interrupts:14.5, cmdline:interrupt, details:IO-APIC  19-fasteoi  ehci_hcd:usb2

userspace:0 id:22, interrupts:9.0, cmdline:interrupt, details:IO-APIC  22-fasteoi  0000:00:11.0

userspace:1 id:2272, interrupts:8.4, cmdline:/usr/bin/firefox, details:hrtimer_start_range_ns (hrtimer_wakeup)

userspace:1 id:2274, interrupts:6.8, cmdline:/usr/bin/firefox, details:hrtimer_start_range_ns (hrtimer_wakeup)

userspace:1 id:2253, interrupts:3.3, cmdline:/usr/lib64/xfce4/exo-1/exo-helper-1, details:do_nanosleep (hrtimer_wakeup)

userspace:0 id:36, interrupts:2.0, cmdline:interrupt, details:PCI-MSI-edge      eth1

userspace:1 id:2068, interrupts:1.1, cmdline:xfce4-panel, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:192, interrupts:1.0, cmdline:kworker/3, details:1      queue_delayed_work_on (delayed_work_timer_fn)

userspace:1 id:2238, interrupts:1.0, cmdline:/usr/bin/python, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:575, interrupts:0.9, cmdline:kworker/1, details:2      queue_delayed_work_on (delayed_work_timer_fn)

userspace:1 id:2066, interrupts:0.9, cmdline:xfwm4, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:2270, interrupts:0.6, cmdline:/usr/bin/firefox, details:Watchdog      hrtimer_start_range_ns (hrtimer_wakeup)

userspace:1 id:1948, interrupts:0.5, cmdline:/usr/libexec/upowerd, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:1531, interrupts:0.5, cmdline:/usr/sbin/gpm, details:do_nanosleep (hrtimer_wakeup)

userspace:1 id:2143, interrupts:0.5, cmdline:/usr/lib/udisks2/udisksd, details:queue_delayed_work_on (delayed_work_timer_fn)

userspace:1 id:2215, interrupts:0.4, cmdline:/usr/bin/xfce4-terminal, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:2065, interrupts:0.4, cmdline:/usr/bin/gpg-agent, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:2074, interrupts:0.3, cmdline:xfdesktop, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:1642, interrupts:0.2, cmdline:/usr/sbin/NetworkManager, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:2123, interrupts:0.2, cmdline:/usr/lib64/tumbler-1/tumblerd, details:schedule_hrtimeout_range_clock.part.26 (hrtimer_wakeup)

userspace:1 id:514, interrupts:0.2, cmdline:kworker/0, details:3      queue_delayed_work_on (delayed_work_timer_fn)

userspace:0 id:1, interrupts:0.2, cmdline:interrupt, details:i8042

userspace:1 id:611, interrupts:0.2, cmdline:kworker/2, details:3      queue_delayed_work_on (delayed_work_timer_fn)

userspace:1 id:2022, interrupts:0.2, cmdline:/bin/sh, details:blk_add_timer (blk_rq_timed_out_timer)

Looks like it's working correctly?

gmgf	12-17-2015 05:22 AM

traditionally ghostscript is updated in new slackware

the latest version is 9.18

http://ghostscript.com/download/

chicken76

12-17-2015 05:29 AM

Quote:

Originally Posted by Nille_kungen (Post 5465101)

While we're at it, these should also be removed:
ftp://ftp.slackware.at/slackware64-14.1/
http://ftp.slackware.at/data/slackware64-14.1/
They've been dead for a while.

gmgf	12-17-2015 06:15 AM

upower -w on 'manjaro'

seem to be similar

upower -w
Total wakeups per minute: 833
Wakeup sources:
userspace:0 id:4082, interrupts:579,0, cmdline:kernel-ipi, details:Rescheduling interrupts
userspace:0 id:4081, interrupts:119,5, cmdline:kernel-ipi, details:Local timer interrupts
userspace:0 id:38, interrupts:38,0, cmdline:interrupt, details:IR-PCI-MSI-edge radeon
userspace:0 id:7, interrupts:23,5, cmdline:interrupt, details:
userspace:1 id:1891, interrupts:19,7, cmdline:kwin_x11, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:0 id:4083, interrupts:4,0, cmdline:kernel-ipi, details:Function call interrupts
userspace:1 id:1899, interrupts:3,2, cmdline:/usr/bin/plasmashell, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:2330, interrupts:2,5, cmdline:/usr/bin/konsole, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:2228, interrupts:2,0, cmdline:/usr/bin/pamac-tray, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1971, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1969, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1970, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1973, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1975, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1968, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1974, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1966, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:2281, interrupts:2,0, cmdline:/usr/bin/pamac-daemon, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1972, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1967, interrupts:2,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:0 id:0, interrupts:1,3, cmdline:interrupt, details:timer
userspace:1 id:2221, interrupts:1,3, cmdline:/usr/bin/msm_notifier, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1962, interrupts:1,2, cmdline:/usr/bin/plasmashell, details:queue_delayed_work_on (delayed_work_timer_fn)
userspace:0 id:19, interrupts:1,0, cmdline:interrupt, details:IR-IO-APIC 19-fasteoi 0000:00:11.0
userspace:1 id:1977, interrupts:1,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1978, interrupts:1,0, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1980, interrupts:1,0, cmdline:/usr/bin/mysqld, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:2340, interrupts:1,0, cmdline:/usr/bin/kactivitymanagerd, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1983, interrupts:1,0, cmdline:/usr/bin/mysqld, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1982, interrupts:1,0, cmdline:/usr/bin/mysqld, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1987, interrupts:1,0, cmdline:/usr/bin/mysqld, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:104, interrupts:0,9, cmdline:kworker/4, details:2 queue_delayed_work_on (delayed_work_timer_fn)
userspace:1 id:85, interrupts:0,9, cmdline:kworker/3, details:1 queue_delayed_work_on (delayed_work_timer_fn)
userspace:1 id:68, interrupts:0,9, cmdline:kworker/2, details:1 queue_delayed_work_on (delayed_work_timer_fn)
userspace:1 id:103, interrupts:0,9, cmdline:kworker/1, details:2 queue_delayed_work_on (delayed_work_timer_fn)
userspace:0 id:4084, interrupts:0,5, cmdline:kernel-ipi, details:TLB shootdowns
userspace:1 id:1707, interrupts:0,5, cmdline:/usr/lib/upower/upowerd, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:0 id:12, interrupts:0,2, cmdline:interrupt, details:i8042
userspace:0 id:17, interrupts:0,2, cmdline:interrupt, details:IR-IO-APIC 17-fasteoi ehci_hcd:usb1, ehci_hcd:usb4, ehci_hcd:usb7
userspace:1 id:1289, interrupts:0,2, cmdline:/usr/bin/NetworkManager, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:11, interrupts:0,2, cmdline:watchdog/0, details:hrtimer_start (watchdog_timer_fn)
userspace:1 id:22, interrupts:0,2, cmdline:watchdog/3, details:hrtimer_start (watchdog_timer_fn)
userspace:1 id:27, interrupts:0,2, cmdline:watchdog/4, details:hrtimer_start (watchdog_timer_fn)
userspace:1 id:32, interrupts:0,2, cmdline:watchdog/5, details:hrtimer_start (watchdog_timer_fn)
userspace:1 id:1979, interrupts:0,2, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:1986, interrupts:0,2, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:0 id:1, interrupts:0,2, cmdline:interrupt, details:i8042
userspace:1 id:1958, interrupts:0,1, cmdline:akonadiserver, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:101, interrupts:0,1, cmdline:kworker/5, details:1 queue_delayed_work_on (delayed_work_timer_fn)
userspace:1 id:1298, interrupts:0,1, cmdline:/usr/bin/wpa_supplicant, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1957, interrupts:0,1, cmdline:/usr/bin/akonadi_control, details:schedule_hrtimeout_range_clock.part.6 (hrtimer_wakeup)
userspace:1 id:1985, interrupts:0,1, cmdline:/usr/bin/mysqld, details:hrtimer_start_range_ns (hrtimer_wakeup)
userspace:1 id:2262, interrupts:0,1, cmdline:kded5 [

brobr

12-17-2015 07:10 AM

I would like to propose inclusion of Inkscape inkscape.org. It is the foss counterpart of Adobe Illustrator, like The Gimp is of Adobe Photoshop. This vector-drawing program is independent of DE and will complement The Gimp, which manipulates pixels.

gmgf	12-17-2015 07:17 AM

again a fix for libcroco-0.6.11

http://ftp.gnome.org/pub/gnome/sourc...co-0.6.11.news

http://ftp.gnome.org/pub/gnome/sourc...-0.6.11.tar.xz

allend

12-17-2015 07:53 AM

Quote:

Dammit. I broke slackpkg. Until Pat gets a fix out, here it is:

There I was, poised with my most delectable paddle, the one with the ostrich feather handle dotted with scorpion and fire ant stingers, but alas :(

Quote:

EDIT: Fixed now; hopefully nobody even got a broken package

was my experience when my local mirror updated.

PS - Kudos to the Slackware crew. -current is tracking extremely well for me.

gmgf	12-17-2015 10:00 AM

new poppler-0.39.0

http://poppler.freedesktop.org/

work, here.

Drakeo

12-17-2015 12:28 PM

Mr Workman you hard work is wonderful. and I see current shaping up. I will repeat my self as I did when 14.1 came out and was terrified because even though current seems to run stable at times or very stable actually. Like I said 2 years ago. if it was released today it would be close to two years before it would become a tool that can be used for long term slow moving software.

Is that good or bad. Well 1337 was the only one that was a serious tool from the go. and 14.0 was ok and got better. 14.1 I freaked I am never going to be able to patch all my stuff to build in the 4.8.2 I thought. LOL
But hey 14.1 turned out to be the work horse hero. This gcc 5.3.0 is serious stuff and I will repeat my self give me two years and this dog will hunt.
Wez that pesqwee wabbit. :).

Quote:

(upower:15170): libupower-glib-WARNING **: Couldn't get total: cannot enable timerstats
Total wakeups per minute: 0
Wakeup sources:
userspace:0 id:0, interrupts:376.0, cmdline:interrupt, details:timer
userspace:0 id:4082, interrupts:0.5, cmdline:kernel-ipi, details:Rescheduling interrupts

ngc891

12-17-2015 03:54 PM

I wish nftables could be updated. It got bug fixes and new features for kernel 4.1. See https://lwn.net/Articles/657933/.

libnftnl: 1.0.3 -> 1.0.5
nftables: 0.4 -> 0.5

And take a look at the conntrack packages, code is 2 years old:
conntrack-tools: 1.4.2 -> 1.4.3
libnetfilter_conntrack: 1.0.4 -> 1.0.5

Thanks,

ReaperX7

12-17-2015 05:46 PM

The Manjaro patch and kernel setting all fix upower-0.9.23, at least on my end anyway. I'll probably drop this into Slackworks for the time being unless/until it goes official.

Suspend works and Hibernate works, though I did have to add the resume=/dev/<swap_partition> to the boot loader command line for the kernel for pm-utils to work properly.

I'll post my kernel config there too.

rworkman

12-17-2015 07:18 PM

Quote:

Originally Posted by rworkman (Post 5464923)

* upower 0.99.3 ?? This has a minor (IMHO) regression with respect to 0.9.23, but we would get a maintained version instead of an abandoned-by-upstream branch. The regression is basically this: upower-0.9.23 advised whether suspend/hibernate was possible itself, i.e. apps like xfce4-power-manager asked upower if it was possible and then invoked the suspend/hibernate by some means (in the case of xfpm, via pm-(suspend|hibernate)). That ability was removed from upower, so now ConsoleKit2 handles that side of things. However, CK2 only implemented a check for whether the hardware is *capable* of suspend/hibernate, which means that there is *not* a check for whether hibernate is actually *possible* - i.e. is there enough swap space available? The result is that in e.g. xfce, the hibernate option is always present in the logout dialog if the system is capable of hibernating, even though the system may not have enough swap space to do so (in my case, there is zero swap space). Is this a sufficient regression to avoid upower-0.99.3? Alternatively, does someone with more time want to grab the code from upower-0.99.3 and make whatever changes are needed to merge it into upstream CK2 (assuming license compatibility) and do a pull request with them? I glanced over it, and it looks relatively trivial to do for someone competent (I think even I can do it, so competence isn't necessarily a requirement ;-) - I just don't have time at the moment). If so, there's already an open issue there on the CK2 github page - just reference that in your PR. I'll be happy to test and add a Signed-Off-By on the PR if you'd like.

Well, I had some time today, so here's the result - please test:
http://www.slackware.com/~rworkman/upower-0.99.3/

ReaperX7

12-18-2015 04:09 AM

Robby, you might want to let Eric know Manjaro has some interesting KDE/Plasma5 patches especially for sddm which might promote some better compatibility in future releases.

Melke

12-18-2015 07:26 AM

Is there a possibility of including a 4.3 Kernel, maybe in testing? Slackware would have skylake compatibility (i'm getting a skylake laptop next month from work).

gmgf	12-18-2015 07:47 AM

Robby, i have compiled all upower and xfce4, package, it seem all work correctly on xfce4,

in kde4, no suspend and hibernate in kde4 menu.

upower seem to work in kde5

rworkman

12-18-2015 08:34 AM

Quote:

Originally Posted by gmgf (Post 5465882)

Robby, i have compiled all upower and xfce4, package, it seem all work correctly on xfce4,

in kde4, no suspend and hibernate in kde4 menu.

upower seem to work in kde5

Hrmm... okay, some of kde4 may need a rebuild to work with upower-0.99.3. I'll try to check on that soon. Thanks for the feedback.

Alien Bob

12-18-2015 09:14 AM

Quote:

Originally Posted by ReaperX7 (Post 5465831)

Robby, you might want to let Eric know Manjaro has some interesting KDE/Plasma5 patches especially for sddm which might promote some better compatibility in future releases.

Robby, can you let ReaperX7 know that the only relevant patch I found is the one that removes support for upower? Probably caused by them supporting systemd instead?

While you're at it, can you also tell ReaperX7 that I might take his posts more seriously if they contain more than just hot air, i.e. where are the pointers to those patches he is talking about?

gmgf	12-18-2015 09:25 AM

Eric, probably here:

https://github.com/manjaro/packages-openrc

because these source are for openrc, and no for systemd.

ReaperX7

12-18-2015 09:43 AM

Quote:

Originally Posted by Alien Bob (Post 5465903)

Considering the fact you work on KDE/Plasma5 I figured I'd try and be nice and a good sport and at least tell you and others about the patches so you see about if they could fit into your work, if they didn't already, and maybe, just maybe be helpful.

Maybe next time I won't post a goddamned thing!

bassmadrigal

12-18-2015 09:56 AM

Quote:

Originally Posted by ReaperX7 (Post 5465914)

I think he was more annoyed with you mentioning patches without providing a link to said patches...

As he said in his post, he could only find one relavent patch that removed upower support.

ReaperX7

12-18-2015 10:02 AM

The link was already there from gmgf's post, just to a subdirectory for upower only. Why should I have to repost something if he can't search the archive himself and do a bit of legwork? Sorry, but I'm not one of those who hand-holds. And besides, if you see my OS posting icon, it was done on my phone so honestly...

gmgf	12-18-2015 10:27 AM

On manjaro all patches are not applied it's like fedora patches,

you have to look in the 'PKGBUILD', too see those used ;)

some patch are obsolet ;)

Didier Spaier

12-18-2015 10:53 AM

On my machine Slackware64-current as of now doesn't boot in UEFI mode, only Legacy.

Am I alone?

Also, I do not see the usefulness of the hardlinks /EFI/BOOT/{huge.s,initrd.img} as grub accepts paths to locations outside /EFI/BOOT and the paths in grub.cfg didn't change since 14.1 anyway.

I am not saying that these hard links are harmful, just wondering. Anyway I will try removing them and see if that makes a difference. Just puzzled as that seems to be the only difference with 14.1 in the /EFI and /isolinux directories.

EDIT: bad mkisofs command, sorry. Still, I will correct it and see what I get with vs without the hard links

EDIT2: booting on UEFI mode works with and without the hard links, that are thus useless unless I miss something.

ReaperX7

12-18-2015 11:01 AM

Quote:

Originally Posted by gmgf (Post 5465936)

On manjaro all patches are not applied it's like fedora patches,

you have to look in the 'PKGBUILD', too see those used ;)

some patch are obsolet ;)

I always tend to look over patches and dry test them before committing them to a SlackBuild of my own. Mostly to see if they work at all. Yes, a lot of stuff gets pushed out over time and across versions, but often I find it useful to see if the patches have internal documentation. I did look over the PKGBUILD scripts. I do this even scanning archives from Fedora, Gentoo, LFS, and even upstream grabs from forums and mailing lists (which is how I got that quirky little Grub-2.02~beta2 btrfs-as-root-on-gpt detection fix patch of mine).

Didier Spaier

12-18-2015 11:06 AM

Let's stay on topic, please.

gmgf	12-18-2015 12:54 PM

Again new cups-filters ;)

http://openprinting.org/download/cup...s-1.5.0.tar.xz

rworkman

12-18-2015 02:04 PM

Quote:

Originally Posted by rworkman (Post 5465893)

Hrmm... okay, some of kde4 may need a rebuild to work with upower-0.99.3. I'll try to check on that soon. Thanks for the feedback.

pprkut found a patch from CK2's maintainer that's been proposed for kde-workspace (v5), and it was a pretty easy backport for kde4, I think. It's still compiling, so I won't know for sure until it finishes and I have a bit of time to play, but I've added the patch to the linked directory above if you want to give it a shot too.

gmgf	12-18-2015 03:18 PM

I try to compile 'kde-workspace' with the patch

gmgf	12-18-2015 03:24 PM

Sorry no compil here

In file included from /usr/include/KDE/KDebug:1:0,
from /tmp/kde-build/kdebase/kde-workspace-4.11.22/powerdevil/daemon/powerdevilpolicyagent.cpp:34:
/tmp/kde-build/kdebase/kde-workspace-4.11.22/powerdevil/daemon/powerdevilpolicyagent.cpp: Dans la fonction membre void PowerDevil::PolicyAgent::onSessionHandlerRegistered(const QString&):
/tmp/kde-build/kdebase/kde-workspace-4.11.22/powerdevil/daemon/powerdevilpolicyagent.cpp:186:20: erreur: POWERDEVIL was not declared in this scope
kDebug(POWERDEVIL) << "Can't connect to systemd";
^
/usr/include/KDE/../kdebug.h:312:87: note: in definition of macro kDebug
# define kDebug(...) for (bool _k_kDebugDoOutput_ = !KDebug::hasNullOutputQtDebugMsg(__VA_ARGS__); \
^
/tmp/kde-build/kdebase/kde-workspace-4.11.22/powerdevil/daemon/powerdevilpolicyagent.cpp:255:20: erreur: POWERDEVIL was not declared in this scope
kDebug(POWERDEVIL) << "Can't connect to ConsoleKit";
^
/usr/include/KDE/../kdebug.h:312:87: note: in definition of macro kDebug
# define kDebug(...) for (bool _k_kDebugDoOutput_ = !KDebug::hasNullOutputQtDebugMsg(__VA_ARGS__); \
^
/tmp/kde-build/kdebase/kde-workspace-4.11.22/powerdevil/daemon/powerdevilpolicyagent.cpp: Dans la fonction membre void PowerDevil::PolicyAgent::setupSystemdInhibition():
/tmp/kde-build/kdebase/kde-workspace-4.11.22/powerdevil/daemon/powerdevilpolicyagent.cpp:576:12: erreur: POWERDEVIL was not declared in this scope
kDebug(POWERDEVIL) << "fd passing available:" << bool(m_managerIface.data()->connection().connectionCapabilities() & QDBusConnection::UnixFileDescriptorPassing);
^
/usr/include/KDE/../kdebug.h:312:87: note: in definition of macro kDebug
# define kDebug(...) for (bool _k_kDebugDoOutput_ = !KDebug::hasNullOutputQtDebugMsg(__VA_ARGS__); \
^
powerdevil/daemon/CMakeFiles/powerdevilcore.dir/build.make:245: la recette pour la cible powerdevil/daemon/CMakeFiles/powerdevilcore.dir/powerdevilpolicyagent.cpp.o a choue
make[2]: *** [powerdevil/daemon/CMakeFiles/powerdevilcore.dir/powerdevilpolicyagent.cpp.o] Erreur 1
CMakeFiles/Makefile2:9479: la recette pour la cible powerdevil/daemon/CMakeFiles/powerdevilcore.dir/all a choue
make[1]: *** [powerdevil/daemon/CMakeFiles/powerdevilcore.dir/all] Erreur 2
Makefile:138: la recette pour la cible all a choue
make: *** [all] Erreur 2
kdebase:kde-workspace failed to build.

gmgf	12-18-2015 03:39 PM

Maybe it's better idea to suggest to Pat to move on kde5 :)

just a joke ;)

All times are GMT -5. The time now is 11:01 PM.

Page 1 of 69

Last »

Show 50 post(s) from this thread on one page