Arch Linux User Repository

I have no idea if this is any help ,, but it may be ;-)

Put brain in gear befor pressing enter11:05:05-->Wed Jun 03-->~ -->valgrind --tool=memcheck spaceclock ==227645== Memcheck, a memory error detector ==227645== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==227645== Using Valgrind-3.16.0.GIT and LibVEX; rerun with -h for copyright info ==227645== Command: spaceclock ==227645== ==227645== Invalid read of size 8 ==227645== at 0x110AD1: void draw_polygon<Vertex*>(Rasterizer, Vertex, Vertex, Color) (in /usr/local/bin/spaceclock) ==227645== by 0x1FFF00066F: ??? ==227645== by 0x5235C1F: ??? ==227645== by 0x5218C7F: ??? ==227645== by 0x110693: ClockApp::ClockApp(int, char, ClockConfig, _GdkPixbuf) (in /usr/local/bin/spaceclock) ==227645== by 0x10FADE: main (in /usr/local/bin/spaceclock) ==227645== Address 0x0 is not stack'd, malloc'd or (recently) free'd ==227645== ==227645== ==227645== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==227645== Access not within mapped region at address 0x0 ==227645== at 0x110AD1: void draw_polygon<Vertex*>(Rasterizer, Vertex, Vertex*, Color) (in /usr/local/bin/spaceclock) ==227645== by 0x1FFF00066F: ??? ==227645== by 0x5235C1F: ??? ==227645== by 0x5218C7F: ??? ==227645== by 0x110693: ClockApp::ClockApp(int, char, ClockConfig, _GdkPixbuf*) (in /usr/local/bin/spaceclock) ==227645== by 0x10FADE: main (in /usr/local/bin/spaceclock) ==227645== If you believe this happened as a result of a stack ==227645== overflow in your program's main thread (unlikely but ==227645== possible), you can try to increase the size of the ==227645== main thread stack using the --main-stacksize= flag. ==227645== The main thread stack size used in this run was 8388608. ==227645== ==227645== HEAP SUMMARY: ==227645== in use at exit: 213,406 bytes in 658 blocks ==227645== total heap usage: 4,414 allocs, 3,756 frees, 653,481 bytes allocated ==227645== ==227645== LEAK SUMMARY: ==227645== definitely lost: 0 bytes in 0 blocks ==227645== indirectly lost: 0 bytes in 0 blocks ==227645== possibly lost: 0 bytes in 0 blocks ==227645== still reachable: 213,406 bytes in 658 blocks ==227645== suppressed: 0 bytes in 0 blocks ==227645== Rerun with --leak-check=full to see details of leaked memory ==227645== ==227645== For lists of detected and suppressed errors, rerun with: -s ==227645== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0) Segmentation fault (core dumped)

Hi installing spaceclock looks as though it has installed correctly,, but ,,

Put brain in gear befor pressing enter17:40:57-->Tue Jun 02-->~ -->spaceclock radar-theme Segmentation fault (core dumped)

Looking back at the spaceclock build I see lots of these warnings, would these be the cause of the failure ?

master.xpm:65:1: warning: ISO C++ forbids converting a string constant to ‘char’ [-Wwrite-strings] 65 | " .++++++++++++++++++++++++++++++++++++++++++++++++++++++++@ ", | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ master.xpm:66:1: warning: ISO C++ forbids converting a string constant to ‘char’ [-Wwrite-strings] 66 | " .++++++++++++++++++++++++++++++++++++++++++++++++++++++++@ ", | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ master.xpm:67:1: warning: ISO C++ forbids converting a string constant to ‘char’ [-Wwrite-strings] 67 | " .++++++++++++++++++++++++++++++++++++++++++++++++++++++++@ ", | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

also there were several warnings like these,

dockapp.h:27:61: warning: dynamic exception specifications are deprecated in C++11 [-Wdeprecated] 27 | DockApp(int ac, char av, const char n, GdkPixbuf p) throw (wm_error); | ^~~~~ In file included from clockapp.cpp:8: rgb_buffer.h: In member function ‘Rgb_buffer& Rgb_buffer::operator=(const Rgb_buffer&)’:

rgb_buffer.h:108:2: warning: no return statement in function returning non-void [-Wreturn-type] 107 | std::copy(b.buf, b.buf + w * h * 3, buf); +++ |+ return *this; 108 | } | ^

Hope this information is useful and thanks for maintaining all the dock apps that do work otb. ;-)

Using your PKGBUILD, wmspaceclock fails to load themes here. Do you know of a solution?

Ha, nice, thanks!

https://gist.github.com/bbidulock/344007bdabd000726df7 is a PKGBUILD that doesn't put files all over the hot place's half acre.

Sorry, there was a stupid error in the PKGBUILD. Fixed.

==> Making package: wmspaceclock 1.2d-3 (Wed 23 Apr 15:11:19 BST 2014) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading spaceclock-1.2d.tar.bz2... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:03 --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading spaceclock-1.2d.tar.bz2 Aborting... ==> ERROR: Makepkg was unable to build wmspaceclock. Is this a hitch or is it dead ?

bidulock does the package work for you with those changes? it fails to load themes here.

bidulock, thank you, I'll check my other wm dock packages too.

I tried again without the +aur