[Desktop-packages] [Bug 1245315] Re: alacarte fails to write a proper Categories=; line to .desktop files
Again, the Categories=; key is not what decides what apps go where, according to the menu-spec. Alacarte writes to ~/.config/menus/applications.menu or similar, which should describe any user-configured overrides to the menus. If XFCE's menu implementation does not support this format, then it is not a menu- spec-compliant menu, and alacarte shouldn't be used to configure it. You can see this file for yourself (it may also be ~/.config/menus/xfce- applications.menu -- check $XDG_MENU_PREFIX), and look at the customizations alacarte is writing to your applications.menu file. I tested this with gnome-panel and gnome-shell, both of which use the gnome-menus library, and Alacarte's customizations came through fine for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1245315 Title: alacarte fails to write a proper Categories=; line to .desktop files Status in “alacarte” package in Ubuntu: Confirmed Bug description: When creating a new menu entry in the Applications Menu of Xubuntu using the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does not enable the writing of a Categories=; attribute in the new .desktop file created in /home//local/share/applications/. Without a recognized and meaningful Categories=; attribute, the new menu entry is relegated by default to the non-specific Other menu category in the Applications Menu of Xubuntu. Moving the newly-created menu entry in question to a more meaningful Applications Menu category (such as, eg, Applications, Office, Systems, etc) by dragging and dropping then fails in alacarte due to the very absence of any Categories=; attribute in the .desktop file. Instead, First, when creating a new menu entry in, for example, Applications, then alacarte should write a corresponding Categories=; attribute line in the newly-made .desktop file. Second, when dragging and dropping the newly-created menu entry in alacarte from, for example, Applications to, for instance, System, then alacarte should amend the Categories=; attribute line in the .desktop file accordingly. Note 1: If alacarte cannot do these things automatically, then it should at least allow the user to choose the Application Menu category, say, from a drop-down list, when creating or editing a menu entry, and write this choice to the corresponding .desktop file in the form of a suitable Categories=; attribute line. Note 2: Resolving this issue by manually editing .desktop files, of course, wholly defeats the very raison d'être of Menu Editor programs such as alacarte. -- System: xubuntu 13.10 32-bit fully up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245300] Re: alacarte does not delete deleted application menu entries
From the menu specification: Hidden should have been called Deleted. It means the user deleted (at his level) something that was present (at an upper level, e.g. in the system dirs). It's strictly equivalent to the .desktop file not existing at all, as far as that user is concerned. This can also be used to uninstall existing files (e.g. due to a renaming) - by letting make install install a file with Hidden=true in it. We show hidden entries because users may want to turn them back on, but the menu implementation should not show these. Yes, the cluttering of alacarte-made-nn.desktop files is an issue. I'll look into solving it in the future by giving the files actually good names. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1245300 Title: alacarte does not delete deleted application menu entries Status in “alacarte” package in Ubuntu: New Bug description: When a menu entry in the Applications Menu of Xubuntu is deleted using the Alacarte Menu Editor, then alacarte (3.10.0-1) does NOT delete its .desktop file. Instead alacarte writes a new Hidden=true line in its .desktop file in /home//local/share/applications/ and it only deletes the entry from the list of menu entries which are shown in alacarte itself. This is wrong. Delete and Hidden are two different things: .desktop files with the attribute Hidden=true should be shown in alacarte as unticked menu entries. Further, by failing actually to delete, alacarte populates /home//local/share/applications/ with increasing numbers of obsolete and dysfunctional .desktop entries. These are difficult to identify and delete manually when browsing /home//local/share/applications/, because alacarte gives all .desktop files which it makes non-specific generic names of the type alacarte-made-nn.desktop. -- System: xubuntu 13.10 32-bit fully up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1245315] Re: alacarte fails to write a proper Categories=; line to .desktop files
The Categories field is only one way that the menu specification decide what subfolder of the menu it will end up with. The menu spec says that ~/.config/menus/applications.menu is what decides where menus go. Alacarte is a menu spec compliant editor. If XFCE does not respect the menu spec, it's their bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1245315 Title: alacarte fails to write a proper Categories=; line to .desktop files Status in “alacarte” package in Ubuntu: New Bug description: When creating a new menu entry in the Applications Menu of Xubuntu using the Alacarte Menu Editor (alacarte 3.10.0-1) then alacarte does not enable the writing of a Categories=; attribute in the new .desktop file created in /home//local/share/applications/. Without a recognized and meaningful Categories=; attribute, the new menu entry is relegated by default to the non-specific Other menu category in the Applications Menu of Xubuntu. Moving the newly-created menu entry in question to a more meaningful Applications Menu category (such as, eg, Applications, Office, Systems, etc) by dragging and dropping then fails in alacarte due to the very absence of any Categories=; attribute in the .desktop file. Instead, First, when creating a new menu entry in, for example, Applications, then alacarte should write a corresponding Categories=; attribute line in the newly-made .desktop file. Second, when dragging and dropping the newly-created menu entry in alacarte from, for example, Applications to, for instance, System, then alacarte should amend the Categories=; attribute line in the .desktop file accordingly. Note 1: If alacarte cannot do these things automatically, then it should at least allow the user to choose the Application Menu category, say, from a drop-down list, when creating or editing a menu entry, and write this choice to the corresponding .desktop file in the form of a suitable Categories=; attribute line. Note 2: Resolving this issue by manually editing .desktop files, of course, wholly defeats the very raison d'être of Menu Editor programs such as alacarte. -- System: xubuntu 13.10 32-bit fully up-to-date To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1245315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
The menu specification, which Unity follows, existed since long before Unity was in the planning stages. Furthermore, the Main Menu application used to edit menus is currently maintained by me, and I am not a Canonical employee. They do not pay me any money, and I have no power over Canonical's choices. The bug here, about not working in Xubuntu, is a combination of two issues: one is that the application did not respect the $XDG_MENU_PREFIX environment, and the other is that due to legacy code, the application depended on a binary installed as part of gnome-panel, so the desktop file editor didn't work. Both have now been fixed. I do not know of Xubuntu's update schedule, but a new unstable release that fixes the issue is out, and the stable release will be part of GNOME 3.8. You can find it here: ftp://ftp.gnome.org/pub/gnome/sources/alacarte/3.7/ If you have other suggestions on how to improve the usability of the menu editor application, please let me know, and I'll try to take your suggestions into account. On Sun, Mar 3, 2013 at 2:26 PM, BavarianPH bavaria...@gmail.com wrote: when ubuntu went to Unity (actually should be called Chaos and Confusion), and then lied about how happy users are about it, they destroyed everthing else easy. Such as the Main Menu. It can no longer be edited to users satisfaction. True it took hours to make my own appnames, to sort them to my own directories, just as I wanted; (because they refused to simplify them and just make them menu text files, that could easily be moved, copied, deleted, backed up, and especially renamed and re-iconed. But atleast I could personalize the menu and thereby streamline my activities.) Now, I am chained to the whims of the programmers, Linux masters, and just as I feared, IT'S REALLY JUST ALL ABOUT MONEY AND POWER, NO open NO freedom! FIX the MENU, I know YOU can, IF you wanted to! I cannot, I am only a dumb, unimportant user!!! BavarianPH -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1079953 Title: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 Status in “alacarte” package in Ubuntu: Confirmed Bug description: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 SYSTEM: Fresh install of xubuntu 12.10 (i386) using the official xubuntu .iso image, fully updated as of today. The 'Main Menu' editor (alacarte) is completely broken in xubuntu 12.10. Changes in the xubuntu Applications Menu made with alacarte are not effected. For example: -- Ticking/unticking boxes in alacarte does not stick. -- New menu items created with alacarte are not put in place. -- Menu items deleted with alacarte remain in place. -- Moving items from one menu folder to another with alacarte no longer works. -- .desktop files of any menu item opened (with or without (!) change) in alacarte simply accumulate in /home/[user]/.local/share/applications, without further effect. -- sudo alacarte in a terminal no longer works. It appears that alacarte is dependent on an item (gnome-desktop-item- edit) provided by the gnome-panel package which is not not compiled with alacarte and which is not otherwise installed under xubuntu. (See also Launchpad Bug #656735 -- https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/656735). However, the full gnome-panel is an alien package under xfce, and it should not be installed under xubuntu as it pulls in a mass of redundant and undesirable non-xfce gnome desktop functionality. (Note: exo-utils for xfce,which provides exo-desktop-item-edit, IS fully installed but this does not resolve the above bugs.) Apart from these bugs, alacarte has limited functionality, it is prone to crashing, and it is awkward to handle. Many of these problems have a very long history and are never properly addressed. It seems better if the alacarte Applications Menu Editor in xubuntu would be replaced as standard (or at least as an option through the (x)ubuntu repos) by LXMenuEditor (http://lxmed.sourceforge.net/). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- Jasper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1079953 Title: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 Status in “alacarte” package in Ubuntu: Confirmed Bug description: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 SYSTEM: Fresh install of xubuntu 12.10 (i386) using the official xubuntu .iso image, fully updated as of today. The 'Main Menu' editor (alacarte) is completely broken in xubuntu 12.10. Changes in the xubuntu Applications Menu made with alacarte are not effected. For example: --
[Desktop-packages] [Bug 1073724] Re: Pointer barriers have gaps along the edge of the screen
Um, as mentioned, Tim's patch actually breaks things as well. And the bug isn't entirely fixed either, just made less noticeable. This is a dup of https://bugs.freedesktop.org/show_bug.cgi?id=48008 ** Bug watch added: freedesktop.org Bugzilla #48008 https://bugs.freedesktop.org/show_bug.cgi?id=48008 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1073724 Title: Pointer barriers have gaps along the edge of the screen Status in “xorg-server” package in Ubuntu: Fix Released Bug description: [Impact] On a multiple monitor setup there is a small gap above the pointer barriers, that allows the mouse to slide through past the barrier, via the edge of the screen. This a particular issue on gnome-shell, since the pointer barriers are used to trap the pointer inside the panel/tray when activating hot- corners. Currently it is extremely hard to land on these hot-corners due to this bug. [TESTCASE] 1. run gnome-shell with atleast 2 montiors in horizontal configuration, 2nd monitor to the right of the primary 2. move mouse towards top-right corner of primary monitor. Pointer should get trapped in the corner of the primary monitor, however it will actually just side over the top of the barrier. With fix in the attached branch, the pointer is correctly trapped. [Regression Pontential] Should be minimal, I have tested under gnome-shell and unity and all hot-corners/sticky edges appear to be working correctly. === Original Bug Report == I have a multiple monitor setup and the pointer barriers seem to have a small (~1px) gap at the edge of the screen. For example in gnome-shell, the panel has barriers on either end, If I move the mouse towards the hot corner (top-right corner of screen) it inevitably just slips over the top of the barrier and onto the next monitor. This bug introduced by the '500_pointer_barrier_thresholds.diff' patch. I have rebuilt the xserver without this patch, and the barriers behave as expected blocking/trapping the mouser pointer in the top corner of the screen. ProblemType: BugDistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 310.14 Tue Oct 9 11:52:41 PDT 2012 GCC version: gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus] CompositorRunning: None Date: Thu Nov 1 08:04:55 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:827c] InstallationDate: Installed on 2012-09-23 (38 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120922) MachineType: Gigabyte Technology Co., Ltd. P67A-UD3R-B3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-18-generic root=UUID=dc987631-dd10-4695-8806-338e780920e2 ro quiet splashSourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: P67A-UD3R-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd07/22/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD3R-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD3R-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P67A-UD3R-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8.4+bzr3407-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati
[Desktop-packages] [Bug 1079953] Re: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10
As the upstream maintainer of alacarte, if you have any of these crashes, I'd love to see them. I do not know of The editing bug may be caused not respecting $XDG_MENU_PREFIX. http://git.gnome.org/browse/alacarte/commit/?id=a4db6799f41947b5cd08231e77d41c561d94170a This commit should fix it. Please try this patch and tell me if it works. Replacing the gnome-panel desktop item editor has been on my list for a little while, but I'm swamped with other tasks so far. I'll try to hack something up this weekend. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1079953 Title: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 Status in “alacarte” package in Ubuntu: New Bug description: Main Menu Editor alacarte is Completely Broken in xubuntu 12.10 SYSTEM: Fresh install of xubuntu 12.10 (i386) using the official xubuntu .iso image, fully updated as of today. The 'Main Menu' editor (alacarte) is completely broken in xubuntu 12.10. Changes in the xubuntu Applications Menu made with alacarte are not effected. For example: -- Ticking/unticking boxes in alacarte does not stick. -- New menu items created with alacarte are not put in place. -- Menu items deleted with alacarte remain in place. -- Moving items from one menu folder to another with alacarte no longer works. -- .desktop files of any menu item opened (with or without (!) change) in alacarte simply accumulate in /home/[user]/.local/share/applications, without further effect. -- sudo alacarte in a terminal no longer works. It appears that alacarte is dependent on an item (gnome-desktop-item- edit) provided by the gnome-panel package which is not not compiled with alacarte and which is not otherwise installed under xubuntu. (See also Launchpad Bug #656735 -- https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/656735). However, the full gnome-panel is an alien package under xfce, and it should not be installed under xubuntu as it pulls in a mass of redundant and undesirable non-xfce gnome desktop functionality. (Note: exo-utils for xfce,which provides exo-desktop-item-edit, IS fully installed but this does not resolve the above bugs.) Apart from these bugs, alacarte has limited functionality, it is prone to crashing, and it is awkward to handle. Many of these problems have a very long history and are never properly addressed. It seems better if the alacarte Applications Menu Editor in xubuntu would be replaced as standard (or at least as an option through the (x)ubuntu repos) by LXMenuEditor (http://lxmed.sourceforge.net/). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1079953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1057600] Re: alacarte crashed with UnicodeEncodeError in save(): 'ascii' codec can't encode characters in position 307-315: ordinal not in range(128)
Pushed a more comprehensive fix to git master. Thanks! Not sure what
flags I'm supposed to set in Launchpad.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alacarte in Ubuntu.
https://bugs.launchpad.net/bugs/1057600
Title:
alacarte crashed with UnicodeEncodeError in save(): 'ascii' codec
can't encode characters in position 307-315: ordinal not in range(128)
Status in Alacarte Menu Editor:
New
Status in “alacarte” package in Ubuntu:
Confirmed
Bug description:
Alacarte crashed on quantal, and killed gnome-panel also. A traceback
is attached.
Something like this should fix the problem:
--- a/Alacarte/MenuEditor.py 2012-08-27 07:08:52.0 +0400
+++ b/Alacarte/MenuEditor.py 2012-09-27 20:09:41.526015518 +0400
@@ -49,7 +49,7 @@
def save(self):
fd = open(self.path, 'w')
-fd.write(self.dom.toprettyxml())
+fd.write(self.dom.toprettyxml().encode('utf-8'))
fd.close()
def restoreToSystem(self):
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: alacarte 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4
Uname: Linux 3.5.0-15-generic i686
ApportVersion: 2.5.2-0ubuntu4
Architecture: i386
Date: Thu Sep 27 19:45:49 2012
ExecutablePath: /usr/bin/alacarte
InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python -OOt /usr/bin/alacarte
PythonArgs: ['/usr/bin/alacarte']
SourcePackage: alacarte
Title: alacarte crashed with UnicodeEncodeError in save(): 'ascii' codec
can't encode characters in position 307-315: ordinal not in range(128)
UpgradeStatus: Upgraded to quantal on 2012-09-23 (4 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev
nopasswdlogin plugdev sambashare tape video
To manage notifications about this bug go to:
https://bugs.launchpad.net/alacarte/+bug/1057600/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
