The older, simpler CPUtemp works in Wheezy.pemasu wrote:That 01mickos`s tempicon is not only incompatible, it is also the reason of hotter laptop.
Dpup Wheezy. Woof-CE built debian wheezy 7.2 packages used
Well.. I did some debugging and it's the icons! I made a test program, just a super simple status icon with 1 of the temperature icons and the behaviour is reproduced. I'll get Joe on to it as it's been stable everywhere else, even in KDE.rcrsn51 wrote:The older, simpler CPUtemp works in Wheezy.pemasu wrote:That 01mickos`s tempicon is not only incompatible, it is also the reason of hotter laptop.
Testprog:
Code: Select all
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <gtk/gtk.h>
#include <gdk/gdk.h>
#include <gdk/gdkkeysyms.h>
#include <glib/gstdio.h>
GdkPixbuf *temp75_pixbuf;
GError *gerror;
void tray_icon_on_click(GtkStatusIcon *tray_icon, gpointer user_data)
{
gtk_status_icon_set_tooltip(tray_icon, ("Hello"));
}
static GtkStatusIcon *create_tray_icon()
{
GtkStatusIcon *tray_icon;
tray_icon = gtk_status_icon_new();
g_signal_connect(G_OBJECT(tray_icon), "activate", G_CALLBACK(tray_icon_on_click), NULL);
temp75_pixbuf=gdk_pixbuf_new_from_file("/etc/tempicon/temp75.svg",&gerror);
gtk_status_icon_set_from_pixbuf(tray_icon,temp75_pixbuf);
gtk_status_icon_set_visible(tray_icon, TRUE);
return tray_icon;
}
int main(int argc, char **argv)
{
GtkStatusIcon *tray_icon;
gtk_init(&argc, &argv);
tray_icon = create_tray_icon();
gtk_main();
return 0;
}
Builds with gcc -Wall -o testing testicon.c `pkg-config --libs --cflags gtk+-2.0`
Kill it with killall testing (as long as you haven't got some other process name 'testing')
- Attachments
-
- temp75.svg.gz
- (288 Bytes) Downloaded 280 times
Puppy Linux Blog - contact me for access
Updated Debian 7: 7.2 released
October 12th, 2013
The Debian project is pleased to announce the second update of its stable distribution Debian 7 (codename "wheezy"). This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems. Security advisories were already published separately and are referenced where available.>>http://www.debian.org/News/2013/20131012
among many other things, they have addressed this one in the update:
http://packages.debian.org/search?searc ... lm-sensors
Any relevance to the problem?
October 12th, 2013
The Debian project is pleased to announce the second update of its stable distribution Debian 7 (codename "wheezy"). This update mainly adds corrections for security problems to the stable release, along with a few adjustments for serious problems. Security advisories were already published separately and are referenced where available.>>http://www.debian.org/News/2013/20131012
among many other things, they have addressed this one in the update:
Code: Select all
lm-sensors - Skip probing for EDID or graphics cards, as it might cause hardware issues
Any relevance to the problem?
My build used fresh debian wheezy packages. The release statement of packages:
http://http.us.debian.org/debian/dists/ ... 86/Release
Archive: stable
Origin: Debian
Label: Debian
Version: 7.2
Component: main
Architecture: i386
The packages should be from Debian 7.2. So I should have included updated packages in use.
http://http.us.debian.org/debian/dists/ ... 86/Release
Archive: stable
Origin: Debian
Label: Debian
Version: 7.2
Component: main
Architecture: i386
The packages should be from Debian 7.2. So I should have included updated packages in use.
Absolutely none.anikin wrote:Any relevance to the problem?
Recently Joe introduced to JWM the ability for non square icons to show as rectangles in the system tray. I suspect it's ok for xpm, png, jpeg but for svg it's broken. I placed an issue on Joe's github page with a link to my above test program. He'll figure it out and at least let me know if it's my fault..
EDIT: fixed now with square (instead of rectangular) icons <-- http://www.murga-linux.com/puppy/viewto ... 387#738387
Last edited by 01micko on Thu 21 Nov 2013, 06:28, edited 1 time in total.
Puppy Linux Blog - contact me for access
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi,
here using wine on puppy and currently wheezy for 4 years with full satisfaction
locating wine ...download here:
http://murga-linux.com/puppy/viewtopic.php?t=53675
better is to use the latest version (although mine is 1.1.20 ... ...yes! some old ms compatible apps work better on that earlier wine version)
Cheers, charlie
here using wine on puppy and currently wheezy for 4 years with full satisfaction
locating wine ...download here:
http://murga-linux.com/puppy/viewtopic.php?t=53675
better is to use the latest version (although mine is 1.1.20 ... ...yes! some old ms compatible apps work better on that earlier wine version)
Cheers, charlie
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi Pemasu,
tons of thanks having upgraded wheezy...! ... and also glad to read from you !
BTW any idea on how to use the "psave" parameter in order to set the grub boot parameters to start on the pupsave ..oops sorry...the wheezysave-XXX specified after that parameter in /boot/grub/menu.lst?
Digging into initrd.gz, I did not find any psave parameter in the init script.
I have opened a thread on that question here...
http://murga-linux.com/puppy/viewtopic.php?t=90255
i suspect it has something to do with the DISTRO_FILE_PREFIX in the FINDING PUPPY FILES section of init script ... (...i should have to spent months to learn script writing before solving that question... )
thanks for any idea
charlie
tons of thanks having upgraded wheezy...! ... and also glad to read from you !
BTW any idea on how to use the "psave" parameter in order to set the grub boot parameters to start on the pupsave ..oops sorry...the wheezysave-XXX specified after that parameter in /boot/grub/menu.lst?
Digging into initrd.gz, I did not find any psave parameter in the init script.
I have opened a thread on that question here...
http://murga-linux.com/puppy/viewtopic.php?t=90255
i suspect it has something to do with the DISTRO_FILE_PREFIX in the FINDING PUPPY FILES section of init script ... (...i should have to spent months to learn script writing before solving that question... )
thanks for any idea
charlie
Last edited by charlie6 on Thu 21 Nov 2013, 09:02, edited 1 time in total.
Fresh manual frugal install....looks good.
# report-video
VIDEO REPORT: Dpup Wheezy, version 3.5.2.8
Chip description:
VGA compatible controller: NVIDIA Corporation NV18 [GeForce4 MX 4000] (rev a4)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri dri2 exa extmod fb fbdevhw glx kbd mouse record shadowfb
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3800+
Memory : 2073MB (322MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Thu 21 Nov 2013 02:50:35 AM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8237 - VIA 8251
# report-video
VIDEO REPORT: Dpup Wheezy, version 3.5.2.8
Chip description:
VGA compatible controller: NVIDIA Corporation NV18 [GeForce4 MX 4000] (rev a4)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri dri2 exa extmod fb fbdevhw glx kbd mouse record shadowfb
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3800+
Memory : 2073MB (322MB used)
Operating System : Unknown distribution
User Name : root (root)
Date/Time : Thu 21 Nov 2013 02:50:35 AM CST
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Unknown
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : VIA8237 - VIA 8251
Nice distro.
Is it possible to put open box/ tint 2 on this, or is it strictly jwm?
I tried, but it goes to the modprobe screen and will only work as xwin jwm.
Just wondering generally, does the package manager update, for instance if there was a new wine or qtractor would that appear in the package manager? I usually just do this with pets, but was looking at the puppy package manager (offline ).
Is it possible to put open box/ tint 2 on this, or is it strictly jwm?
I tried, but it goes to the modprobe screen and will only work as xwin jwm.
Just wondering generally, does the package manager update, for instance if there was a new wine or qtractor would that appear in the package manager? I usually just do this with pets, but was looking at the puppy package manager (offline ).
Charlie6. I think that there isnt any 'psave' functionality in init script. I find no reference into it when I searched through init script. I think that you are on your own with 'psave' functionality. As you probably noticed pupsaves are recognized with PUPSAVE references...and there is a lot of them to create functionality in different situations. But no 'psave'.
Smithy. There is no reason why openbox with tint2 should not work. I believe that in the past people have used them a lot. Those who have used them, probably have ready made packages for it. I think I have provided them also...by just uploading them to some repos....
I believe I uploaded openbox-fbpanel-tint2 pets to the exprimo repo in smokey01.com. they should provide templates how to do it. I had 'wmswitcher' included in exprimo to provide easy windowmanager switching though and /etc/xdg/templates/_root_.jwmrc edited to show that wmswitcher in jwm main menu.
I havent played with them in dpup wheezy, since I have been happy with jwm. I use openbox with lxde in Lubuntu 64 bit and jwm with Puppy. So...happy experimenting.
PS. Radky probably have openbox related ready packages. He has recently updated that kind stuff in recent Lucid Puppy releases.
Smithy. There is no reason why openbox with tint2 should not work. I believe that in the past people have used them a lot. Those who have used them, probably have ready made packages for it. I think I have provided them also...by just uploading them to some repos....
I believe I uploaded openbox-fbpanel-tint2 pets to the exprimo repo in smokey01.com. they should provide templates how to do it. I had 'wmswitcher' included in exprimo to provide easy windowmanager switching though and /etc/xdg/templates/_root_.jwmrc edited to show that wmswitcher in jwm main menu.
I havent played with them in dpup wheezy, since I have been happy with jwm. I use openbox with lxde in Lubuntu 64 bit and jwm with Puppy. So...happy experimenting.
PS. Radky probably have openbox related ready packages. He has recently updated that kind stuff in recent Lucid Puppy releases.
3.5.2.8
Geeeee... I'll try just once more to get this to the right thread
Upgrade to 3.5.2.4
All went well (desktop icons to be fixed & background) but retained my wbar settings from 3.5.2.4 and...
'it's looking very good pemasu, thanks for continuing with puppy!'
On with the testing.
>>>---Indian------>
Upgrade to 3.5.2.4
All went well (desktop icons to be fixed & background) but retained my wbar settings from 3.5.2.4 and...
'it's looking very good pemasu, thanks for continuing with puppy!'
On with the testing.
>>>---Indian------>
- Attachments
-
- desktop-1.png
- (139.54 KiB) Downloaded 413 times
Cloud Computing For Every Puppy (a .pet)
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
[url]http://murga-linux.com/puppy/viewtopic.php?t=69192[/url]
Anikin. The eee.ko module was found here:
/lib/modules/3.5.2-dpup/kernel/drivers/platform/x86/eee.ko
# modinfo eee
filename: /lib/modules/3.5.2-dpup/kernel/drivers/platform/x86/eee.ko
description: Support for eeePC-specific functionality.
author: Andrew Tipton
license: GPL
depends: i2c-core
vermagic: 3.5.2-dpup SMP mod_unload modversions CORE2
and...it should not matter where it is placed when it is found by modprobe. I think.
If you move the location, remember to run in console: depmod
...so that the new location has been noticed. I think that I have placed eee.ko to 2 places depending on what distro I have created. The acpi folder is the other one.
Otherwise...I should you check with command dmesg....if there is something outputted there which would tell what goes wrong.
/lib/modules/3.5.2-dpup/kernel/drivers/platform/x86/eee.ko
# modinfo eee
filename: /lib/modules/3.5.2-dpup/kernel/drivers/platform/x86/eee.ko
description: Support for eeePC-specific functionality.
author: Andrew Tipton
license: GPL
depends: i2c-core
vermagic: 3.5.2-dpup SMP mod_unload modversions CORE2
and...it should not matter where it is placed when it is found by modprobe. I think.
If you move the location, remember to run in console: depmod
...so that the new location has been noticed. I think that I have placed eee.ko to 2 places depending on what distro I have created. The acpi folder is the other one.
Otherwise...I should you check with command dmesg....if there is something outputted there which would tell what goes wrong.
Moved it back and forth, depmoded, - no joy ...
and then applied this little, dirty trick: "acpi_enforce_resources=lax" as a kernel parameter. Works fine. I've had this issue before in dpups. Must be a unique Debian thing - no such problem in other puppies. OK, if anyone has issues with fan control, the above will solve it. Not a clean solution, though - a stopgap measure until something better is found.
and then applied this little, dirty trick: "acpi_enforce_resources=lax" as a kernel parameter. Works fine. I've had this issue before in dpups. Must be a unique Debian thing - no such problem in other puppies. OK, if anyone has issues with fan control, the above will solve it. Not a clean solution, though - a stopgap measure until something better is found.
- Attachments
-
- eee.jpeg
- (36.5 KiB) Downloaded 859 times
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi again Pemasu!
could not resist to load 3.5.2.8 ... and thanks for it ! posting from a pristine boot !
3.5.2.8 boots OOTB on my not that so old PIV with 82845G (Brookdale... ) video chip: no black X desktop screen ...that's really charming!
gnumeric-1.10.17 as also abiword-2.9.2 report when wanting a preview:
FF 25.0.1: seems needing a few more time to start.
cheers, charlie
could not resist to load 3.5.2.8 ... and thanks for it ! posting from a pristine boot !
3.5.2.8 boots OOTB on my not that so old PIV with 82845G (Brookdale... ) video chip: no black X desktop screen ...that's really charming!
gnumeric-1.10.17 as also abiword-2.9.2 report when wanting a preview:
fix: just need to create a symlink /usr/bin/evince-previewer to /usr/bin/evince# abiword
** (evince:10339): WARNING **: Error launching previewer: Failed to execute child process "evince-previewer" (No such file or directory)
FF 25.0.1: seems needing a few more time to start.
cheers, charlie