Image 01
profile-image

qb89dragon

Chris Hughes Vancouver, Canada
System Software
Utilities
Various Gnome Stuff
test
Cairo Menu

Utilities 34 comments

Score 67.1%
Jan 02 2011
If you want to chat more about it, my msn address is hughescih _at_ hotmail _dot_ com - Aug 03 2009
I took a look recently at the gnomenu project and while it has come a long way, was slow and based itself off very old code I wrote for Vista Menu that wasn't as efficient as this menu engine is. I'm working on a number of new concepts and features for this menu, and you're welcome to share ideas or use the code from this menu to speed up and improve gnomenu. But I don't have the time to spend rewriting a menu where I feel a rewrite from scratch is due.
Recreating gtk widgets en-mass, using xdg and parsing the recent items internally, passing many callbacks and not running code in tandem or behind timers are just some of the reasons vistamenu/gnomenu is relatively slow. - Aug 03 2009
Wacom Control Panel

System Software 303 comments

Score 76.7%
Jun 02 2011
I'm afraid everything points to arch not supporting multiple input devices through HAL. This was quite a challenge and involved a restructuring of parts of HAL - to the best of my knowledge I believe alot of this was undertaken by ubuntu devs, hence why it may take a while to port over a new HAL into Arch. If you want to go ahead and post on Arch's forum, you may get a clearer answer as to why as I don't follow the development of Arch. But based on what you've posted here it very clearly points to that being the cause of the issue you're having. - Jul 14 2009
You have an older version of the wacom HAL fdi files. Yours is equivalent to Ubuntu 8.04 - where hotplugging was supported but it only gave you a mouse, no pressure, pad or multiple inputs supported. Until your distro gets updated, use version 1.8, it's not a bug or problem in my code, you just need to wait until it's updated for your distribution. - Jul 13 2009
Two questions to help track this one down:
1) When you installed 1.9, the first time you started it up it should have prompted you to remove old configuration, you put in your password, then it asks you to log out. Did that happen?

2) What is the output of xinput --list - Jul 09 2009
If your distro doesn't have that patch, then go with version 1.8 - the link to that version is kept on this page for that reason. But when your distro does, it's recommended to switch to the latest version as I'll be adding stuff like input redirection configuration and more cool features. - Jul 08 2009
This is an issue way beyond the application I wrote. It's to do with the way X11 (the standard window manager on linux) redirects inputs. I may be able to find and link you to an option to disable this through the application though.

I need to know some more information however, firstly what distribution of linux, what version of what distribution.
Then I need to know what video card you are using in your laptop, if it is nvidia, or ati please tell me if it is the open source or the manufacturer's drivers. If it is nvidia, please tell me if you have TWINVIEW enabled (this is really important).
If you have neither nvidia or ati, just copy and paste the output of the command 'lspci' from a terminal to here.

Also what version of the wacom control panel are you using? If it is anything other than the latest version, then it configures the tablet in an older way that may be less configurable. - Jul 07 2009
Ok. It's been fixed! - Jul 05 2009
Hi there,
I am aware of this problem and I plan to remove all xorg.conf configuration and work solely with the new HAL system that now fully supports pressure sensitivity. Please be patient and I'll get it done as soon as possible so that there is a config-free process for configuring a tablet. For now though, you can remove the lines from xorg.conf by unchecking the box in the 'options' screen before shutting down the computer to save the hassle of rewriting your xorg.conf from scratch. - Jul 05 2009
Ok. Fixed that one too for ya! - Jun 26 2009
Let me know if the button mapping is correct now. - Jun 25 2009
Ok. I found the problem and fixed it for the buttons changing multiple times. - Jun 25 2009
Hi there, sorry for not getting back to you - there was alot to look at in your post and I have been very busy with work lately. I will take a look at the buttons editing one or more items, but I can't fix the mapping until that is resolved. Your fourth issue is related to pygtk and how it renders large lists. For the button mapping, I had to guess all the other tablets and then rely on user feedback to fix them, so I would appreciate your assistance in getting it right. I haven't had to reboot when testing on two ubuntu 9.04 installs. What version of what distro required you to reboot.
Another thing, there will be no rpm distro versions released for the next while because some of them cannot work with the gksu command that is required.
When I fix the button mapping on the next release on here, please let me know the correct button mapping and I'll include that. - Jun 25 2009
Nope, serial tablets aren't supported I'm afraid. Your best bet is to follow the guide to configure your xorg.conf manually. Install the wacom-tools package and run wacomcpl from the command line. - Jun 20 2009
how did you set it to 'relative mode' in intrepid? what command or utility did you use? - Jun 08 2009
I have no idea what relative mode should do. This came from alexander macdonald's side of the code (the pressure support screen).
Anyhow, it looks like everything else is working fine for you, you just need to tell gimp to use your tablet.
To do this, follow these steps:
1. Open GIMP
2. In the Edit menu, click on preferences
3. Click on Input Devices
4. Click on Configure Extended Input Devices
5. For the devices; stylus, eraser and cursor, set the Mode to 'Screen'
6. Click Save, then Ok and you're done! - Jun 06 2009
Try disabling and re-enabling pressure support with the latest version. If that doesn't fix it, send me your entire xorg.conf file. - Jun 05 2009
What exactly isn't working with the pressure and pad? What is it doing?
Can you send me the output of lsusb in a terminal - that helps me make changes to your exact model's info.
Thanks! - Jun 04 2009
I've updated the software. Thanks for the help fixing that. - Jun 03 2009
Can you please open a terminal, type lsusb and hit enter. Then copy and paste the output to a reply here. That way I can know the specific model you have.
Thanks - May 31 2009
I have noticed that issue, and will look into it. When you check or uncheck tablet support it adds or removed the relevant lines in xorg.conf. It may be an issue with the lines that it has added, may be an issue introduced by a new xserver version with ubuntu 9.04 (as the same configuration has worked fine in the past for me), or could be caused by the HAL not being disabled for tablets. I'll look into it and get that fixed. - May 28 2009
Thanks. I'm glad you like it - I was too frustrated with the lack of support for wacom tablets, and saw no resolution in sight, hence was compelled to write the utility.
I tested it on a brand new install of ubuntu 9.04 and found that it worked around the HAL fdi files and there was no need to delete them, simply unchecking tablet support put the system back to it's default settings and functionality. - May 28 2009
Ok. I know what the problem is, you're missing a serverlayout section, and the software isn't adding one if it is missing. I can fix that in a day or so, but for now, go to a terminal and type sudo gedit /etc/X11/xorg.conf

and paste this at the end of the file and log out/log in again:

Section "ServerLayout"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents" # For non-LCD tablets only
InputDevice "pad" "SendCoreEvents" # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
Identifier "Default Layout"
Screen "Default Screen"
EndSection - May 24 2009
Ok. I know what the problem is, you're missing a serverlayout section, and the software isn't adding one if it is missing. I can fix that in a day or so, but for now, go to a terminal and type sudo gedit /etc/X11/xorg.conf

and paste this at the end of the file and log out/log in again:

Section "ServerLayout"
InputDevice "stylus" "SendCoreEvents"
InputDevice "eraser" "SendCoreEvents"
InputDevice "cursor" "SendCoreEvents" # For non-LCD tablets only
InputDevice "pad" "SendCoreEvents" # For Intuos3/CintiqV5/Graphire4/Bamboo tablets
Identifier "Default Layout"
Screen "Default Screen"
EndSection - May 24 2009
Did you log out and log back in again after enabling pressure support?

Can you post your xorg.conf file in here?

I would also expect some breakages in future as one of the release goals for karmic I believe is to have working pressure support through HAL, instead of X11. - May 24 2009
None of that output indicated there was an error. Can you please send me the output of the command lsusb from a terminal. Also does the application show you a photo of your intuos 2 tablet in the top left? (indicating that it has been detected). Does the pen work as a regular mouse? Does the pressure support work at this point? Have you modified your xorg.conf file yourself beforehand? - May 23 2009
If you don't get the extra options, you may have encountered an error.

Please tell me what distribution you are using, as well as that distribution's version.

Then go to a terminal, and run the following:

/usr/share/wacom-utility/wacom_utility.py

and copy and paste any text that appears in the terminal into this site.

Thanks! - May 22 2009
Either you haven't enabled pressure / pad support in the options dialog, or you don't have wacom-tools (a dependency) installed. - May 11 2009
send me a note with your email address and I'll send it along. gtk-apps only lets you upload one package. - May 11 2009
I don't have any webhosting right now, but I'm setting up a sourceforge page for it right now. It will take about three days to do, so send me a note with your email address and I'll send you an RPM package and/or the source code. - May 09 2009
Thanks. Glad you like it. Please let me know of anything that isn't working right or that can be improved. Especially if the pad buttons are in the wrong order on your model of tablet. - May 08 2009
Vista Start Menu for Gnome Panel

Various Gnome Stuff 381 comments

Score 50.0%
Nov 23 2008
Vista Menu has been discontinued, it's now called Gno-Menu and is available through launchpad. I can send you a translation template for Russian and would very much appreciate your help with translation. - Jan 04 2009
Thanks for your help. That would be great if you could send those to me. Or I could send you the newest release of the menu - the one on the site is outdated, I just haven't had the time to package the new one and get it on here. - Nov 08 2008
I believe it's deskbar-applet now.
I will release the next version of it soon where changes are applied automatically without having to restart the menu. - Nov 08 2008
nobody's had a similar error. I'm using ubuntu 8.04 myself, so it's likely a configuration problem at your end. Try making a brand new user account and trying it there with a logoff. Did the debug show anything on the account that didn't have any icons. - Sep 09 2008
Weird, what version of what distro are you on?
Try reinstalling it (and not the .deb package)
Can you run it from a terminal Vista_Menu.py , then leave the blank terminal window, and add it to the panel - leaving the terminal, and then all the debugging you get in the terminal window, you can paste back in here. - Sep 09 2008
the program expects your XDG menu list to be in the location /etc/xdg/menus/applications.menu . It's worked for everyone so far across quite a range of distributions - as it's the first time I've heard of this error happening. Has something changed about the way menus are stored in debian? - Sep 01 2008
Try running from terminal ./Vista_Menu.py run-in-window and paste any debugging output here. - Aug 30 2008
Thanks for the offer to translate it. I can do it myself if you can send me the text you would like in the button. - Aug 09 2008
Try deleting the .VistaMenuSettings.xml file in your home directory (it's a hidden file). Then go to a terminal and run Vista_Menu.py run-in-window
and see what happens, copy and paste any error or traceback output and I can find what is wrong for ya. If you would like to develop themes, send me a message with your msn contact name and I can help you out further. - Jul 29 2008
It should work. If you need any further modules, please let me know so that I can post installation instructions to fedora users.
Having a packaged version for fedora would be great, hopefully can do sometime in the future. - Jul 24 2008
If you send the icon theme to me, it must match the format of an existing theme. These are in the install package under /Themes/Icon. Then I can include it in the next release. - Jul 21 2008
You will need to use your package manager to search for the packages as the names may have changed. Either that or download and configure them manually. The error you have received is caused by not having deskbar applet installed. - Jul 13 2008
What distribution (i.e Ubuntu, Fedora, Redhat etc) are you using?

Have you installed the required dependency packages?

What is the output of running Vista_Menu.py run-in-window from a terminal?

I don't speak spanish much so please keep it simple then I can understand! =) - Jul 09 2008
Thanks for the offer. I would very much appreciate your translation. Message me with your email or MSN contact ID and I can send you a translation template. - Jul 02 2008
They both came from this amazing artist's gallery:
http://nambroth.deviantart.com
- Jul 02 2008
If you go to Alacarte (your menu editor), and right click on synaptic under system tools, what command is it executing? - Jul 02 2008
Delete your .VistaMenuSettings.xml in your home directory (hidden file). It happens that some themes arent fully updated yet to support the new software. - Jun 27 2008
Do you know a better way than parsing applications.menu? - Jun 26 2008
The search bar isn't selectable, just type away and your text will go in it. The menu contents don't match because of programs installed under other desktop environments, such as KDE. This is an issue with the python XDG backend. - Jun 26 2008