Skip to main content
22 events
when toggle format what by license comment
Oct 21, 2021 at 15:26 history edited Peter Mortensen CC BY-SA 4.0
Copy edited (e.g. ref. <https://en.wikipedia.org/wiki/Windows_XP>).
Mar 29, 2013 at 20:36 history made wiki Post Made Community Wiki by uınbɐɥs
May 25, 2011 at 9:12 comment added ptrcao In WinXP there is no process taking up port 8140. Can I launch StackApplet from within terminal to see errors? If so, what command do I use? Basically launching it via the start menu, nothing appears to happen...
May 25, 2011 at 6:54 comment added ptrcao Sounds good. Though, if you want me to try anything in the meantime, just let me know. I'll try vacating the port and seeing if it makes a difference...
May 24, 2011 at 20:05 comment added Nathan Osman @ptr: It could be. I'll let you know when I make the next release with the modified port so that you can try it.
May 24, 2011 at 20:00 comment added ptrcao No problem, thanks for programming StackApplet. :) Do you think the problem is the same with Windows XP? I had a similar issue with launching StackApplet in Windows...
May 24, 2011 at 19:50 comment added Nathan Osman @ptr: I haven't released v1.5 yet, so yes - I can and will change the port number. Thanks for helping me with this - I appreciate it.
May 24, 2011 at 19:45 comment added ptrcao In System Monitor I found the process "python usr/bin/system-config-printer-applet" - this was the only python process running. When I stopped this process and launched StackApplet, it worked. It appeared some vital printing applet was occupying the port/address. Can you make StackApplet use a different, vacant port?
May 24, 2011 at 17:12 comment added Nathan Osman @ptr: It should be as simple as 'kill xxx' where xxx is the ID of the process. To find the ID of the StackApplet process, you will need to use Debian's system monitor tool (I'm not sure if that's what it's called, but basically it's the tool that lists all of the currently running programs - StackApplet will probably show up somewhere under Python). Once you find the process ID and 'kill' StackApplet, then you should have no problem running StackApplet from the terminal.
May 24, 2011 at 11:01 comment added ptrcao Ok, so it's giving the same error: address already in use. How do I vacate the address? What command?
May 24, 2011 at 5:59 comment added Nathan Osman @ptr: 'python /usr/share/stackapplet/stackapplet.py'
May 23, 2011 at 22:36 comment added ptrcao What commands shall I use to launch it in terminal?
May 23, 2011 at 17:00 comment added Nathan Osman @ptr: If everything is empty, that means that the translation subsystem is not functioning properly. Is there any way you could make sure that there are no running instances of StackApplet and then try running it from the terminal again? It sounds like it is still running somehow. If you can get it running in a terminal, then we'll hopefully see some error messages that will make it easier to pinpoint what exactly the problem is.
May 23, 2011 at 9:36 comment added ptrcao I tried visiting localhost:8140 and whilst I could see a heading "StackApplet Preferences", all that appears on the page are empty bullet points, an empty dropdown menu, radio buttons and check boxes with no accompanying text. Can you suggest anything else? I'm happy to provide any info you think might be helpful and diagnosing the problem.
May 22, 2011 at 19:29 comment added Nathan Osman @ptr: It must be running somewhere. Since it sounds like the web interface is running, you can simply open your browser and visit 'http://localhost:8140'. That will bring up the preferences page which will allow you to configure the application.
May 22, 2011 at 8:24 comment added ptrcao In case this tells you anything, peter@debian-peter:~$ lsof -i :8140 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME python 6987 peter 7u IPv4 52025 0t0 TCP localhost:8140 (LISTEN)
May 22, 2011 at 7:16 comment added ptrcao I can't see anything in the notification area, especially not the stackapp icon. Other active programs in the notification area include Thunderbird and Compiz Fusion. Do you perceive any conflict here?
May 22, 2011 at 6:27 comment added Nathan Osman @ptr: It seems like the port that StackApplet uses is already in use (StackApplet uses port 8140 for managing preferences). Can you check if StackApplet is already running? When it is working properly, you should see an icon in your notification area (the panel at the top of your desktop).
May 22, 2011 at 6:22 comment added ptrcao As requested see OP.
May 22, 2011 at 6:22 history edited ptrcao CC BY-SA 3.0
added 1858 characters in body
May 22, 2011 at 5:58 comment added Nathan Osman I'm not sure why it wouldn't work in Windows XP, but it's easier to debug in Debian. Try starting StackApplet by running 'python /usr/share/stackapplet/stackapplet.py'. Please post any output you receive.
May 22, 2011 at 5:39 history answered ptrcao CC BY-SA 3.0