You are not logged in.
Hi,
I am running the latest version of #! on a Samsung NC10 netbook. I switched to using wheezy as the repo.
Ever since a couple of weeks ago, when I wake up from sleep mode, I have empty spaces added to the right-hand side of my tint2 panel in between my tray icons and the time/date. When I right click on them, nothing happens--no menu, no nothing. Each time I sleep and wake up the machine, another space is added to the right-hand side. This consequently shortens my two desktop spaces in the tint2 bar. The only way to fix this is to restart tint2 or the computer.
Has anyone experienced this, and how can I fix it? Thanks.
Offline
i have experienced empty tint2 items. not sure if it was after sleep, could very well be. never noticed they were growing with each sleep-cycle, but never paid attention to it either, always ignored it a bit, and honestly never really looked into why they appeared there. the one thing i did find out was that one of those blank spaces was due to the battery icon, which i hid. apparently you can say 'battery=0' as well as 'battery-hide=1' and only the hide-option works and removes the space (this is from the top of my head, have no linux in front of me). you might want to look into that?
Offline
No, all my icons remain, but they are just "pushed away" by blank space from the time/date. It's so weird!
Offline
TInt2 system tray is doing the same thing on my machine, too. If anyone figures out a solution, I would really like to know.
Offline
Try uninstalling tint2 and install the latest version from svn:
http://code.google.com/p/tint2/wiki/Ins … l_Manually
http://peppermintos.us/how-to-build-pro … st-sources
If the problem still exists, I would file a bug report:
Note: ** Please read before posting **
BTW if you wish to contact me, send me an e-mail instead of a PM.
Offline
I'm having the same problem with no fix yet :\
"Let's paint some happy little trees there, don't worry you won't damage the canvas. We don't have mistakes here, we just have happy accidents."
Offline
Try uninstalling tint2 and install the latest version from svn:
http://code.google.com/p/tint2/wiki/Ins … l_Manually
http://peppermintos.us/how-to-build-pro … st-sourcesIf the problem still exists, I would file a bug report:
I can't seem to get the imlib2 dependancy for it, when I try and install imlib2 from a .deb it says I already have that version yet the cmake says the imlib2 dependency is not fulfilled.
"Let's paint some happy little trees there, don't worry you won't damage the canvas. We don't have mistakes here, we just have happy accidents."
Offline
@reformat: often when this kinda thing happens, cmake is looking in a different directory than where your imlib2 is installed. you can probably configure where cmake looks through some flags or something, it may even say so in the errors it gives.
Offline
@reformat: often when this kinda thing happens, cmake is looking in a different directory than where your imlib2 is installed. you can probably configure where cmake looks through some flags or something, it may even say so in the errors it gives.
It seems to be calling pkg_check_modules to find it, which is failing on imlib2 for some reason.
EDIT: Just noticed it isn't actually finding any of the packages
Last edited by reformat (2011-05-31 13:57:44)
"Let's paint some happy little trees there, don't worry you won't damage the canvas. We don't have mistakes here, we just have happy accidents."
Offline
Hi to everybody,
I do experience the same problem with widening gap right to the systray area - the area is active and shows battery data.
I have also tried several changes to config file but with no success. I even deleted the battery section - the problem persists:(
Regards,
D*
Join the movement: http://thezeitgeistmovement.com/
Offline
I occasionally have the same thing, but restarting tint fixes it
Artwork at deviantArt; Iceweasel Personas; GDM #! Themes;
SLiM #! Themes
Offline
Found this workaround on Arch forums: https://bbs.archlinux.org/viewtopic.php?id=111712
but can't quite get it to work. Anyone else have success with this?
Last edited by badkarma (2012-06-30 00:25:52)
Offline
Got it to work. I created a script in /etc/pm/sleep.d named "99tint2", made it executable with 'chmod +x'.
Contents of the script:
#!/bin/bash
case $1 in
hibernate|suspend)
;;
thaw|resume)
export DISPLAY=:0 &&
sleep 3 &&
killall tint2
;;
*)
;;
esacSeems to work OK!
[EDIT]
Works if I click "suspend" from the exit menu, but not if I close the lid of the netbook, force computer to suspend, then reopen the lid to wake from suspend.
Last edited by badkarma (2012-06-30 00:59:32)
Offline
That is due to a bug in the xfce4 power manager applet. Every time it wakes from sleep or hibernate it bumps itself over a notch.
I also had trouble with it silently crashing after waking from sleep mode. I almost found that out the hard way. I have my Netbook set to sleep when the screen is closed. One day I was using the Netbook when a friend called to ask me to go somewhere with her. So I closed the screen, unplugged it, put in its Neoprene sleeve and zipped it up. Fortunately I had it in my lap because I noticed the case getting alarmingly warm. When I opened it and pulled the Netbook out it was burning hot! The xfce4 power manager had crashed and the computer didn't sleep when I closed the screen. So it was merrily chugging away at full power mode (since it had been on AC when I closed the screen). If I had put it on the back seat it would have continued to heat up and I doubt it would have survived the hour long drive.
There was a thread about this not too long ago. If I'm remembering correctly the crash would occur when the power state changed while in sleep mode. In other words, you sleep it on battery, then plug it in before waking it (or vice-versa) and *poof* no more power management.
I switched to the Gnome power manager and never looked back. Only problem I've had with that is it thinks I have 2 batteries, but it's purely a cosmetic defect. Functionally it has worked flawlessly.
There are only 10 kinds of people in the world, those who understand binary, and those who don't.
Offline
Oh, and dalbrecht77,
Please check the date of the thread before replying. Bumping old threads is poor net etiquette. Old threads often have out of date info and advice that can cause problems for people, so they should not be bumped back to the top. Start a new topic if there are no current threads.
And yes, I know I just bumped it as well, but since there were replies as recent as yesterday I didn't notice it was a year old thread until I looked at your post.
There are only 10 kinds of people in the world, those who understand binary, and those who don't.
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.