[Desktop-packages] [Bug 499754] Re: I can not edit menu entries in alacarte at random - Ubuntu Lucid (10.04)
I'm still running Ubuntu 10.04 LTS with GNOME 2.30 at this late date and
just encountered this problem after installing LibreOffice 4.3.5, using
a DEB archive obtained from LibreOffice.org. I didn't like the way the
installer put the entries in the Applications menu and began editing the
menu with alacarte (System -> Preferences - > Main Menu). During this
edit I made a mistake, deleting a menu item, so I clicked on the
"Revert" button, after which havoc ensued. A number of custom sub-menus
changed from their original names to "alacarte-made-x", where "x" was
some number, and those entries became non-editable. The problem appears
to have been caused by alacarte improperly deleting one or more of its
.directory files in /home//.local/share/desktop-directories and
*possibly* by the LibreOffice installation causing additional
corruption. I was able to recover by using the following steps.
1. In a terminal window in my home directory, I executed
sudo chown -R .config/menus
sudo chown -R .local
(Substitute your user name for .) This fixes improper file
ownership issues. Some of the alacarte-made non-editable menu entries
now became accessible with the Properties button, but several menus
became cross-linked, so that when the name of one menu was changed in
the menu editor, the name of another, completely unrelated menu also
changed.
2. I looked in my .config/menus directory to find an "undo" .menu file
with a time stamp just after the new package was installed. This was
easy, because the file with LibreOffice 4.3.5 had entries containing
"4.3.5" that could be found with a text editor. I renamed
applications.menu as applications.menu.bak, then copied my chosen .menu
.undo-xx file to applications.menu.
3. The first two steps still didn't fully correct the problem, but by
looking in .local/share/desktop-directories and examining the contents
of the various .directory files and comparing what alacarte-made-x
entries there were displayed in my Applications Menu. From this I was
able to deduce which .directory files were missing and using gedit I was
able to recreate them, using the existing .directory files as a
template. Once the missing alacarte-made-x.directory files were
restored, the cross-linking of submenu entries in the Applications menu
was fixed, allowing all submenus and items to be edited normally again
with the Properties button.
A more drastic alternative would have been to wipe out the contents of
.local/share/desktop-directories and .config/menus and start over, but a
bit of patience in performing manual repairs as described above saved me
many, many hours of menu creation and customizing.
I think this may not be a bug in alacarte as such, but a general lack of
robustness in the GNOME 2 menu and the design of alacarte, in that
alacarte is unable to detect corruption in the menu files or missing
directory files, and simply gets confused. The utility should have
automatic error detection and correction built in, or a button or menu
that can be invoked manually by the user to repair the menu structure
when something goes amiss. There may also be problems with the way the
Revert feature works in alacarte, which *may* have been the cause of the
problem in this instance.
--
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/499754
Title:
I can not edit menu entries in alacarte at random - Ubuntu Lucid
(10.04)
Status in alacarte package in Ubuntu:
Expired
Bug description:
Binary package hint: alacarte
Hello,
Sometimes I am unable to edit a menu entry in alacarte, but sometimes I can.
If I click on the properties button for the menu entries, it sometimes fails to
open, however, If I continue to click on the properties button to other random
menu entries, I will be able to edit the one I want to edit eventually. It
seems that when I repeatedly click on the same properties button that failed to
open, it makes the problem worse. This applies to Ubuntu Lucid Alpha 1.
Running alacarte in the terminal provides this output as soon as a
properties button fails to open:
james@Lucid:~$ alacarte
Traceback (most recent call last):
File "/usr/lib/pymodules/python2.6/Alacarte/MainWindow.py", line 625, in
on_properties_button_clicked
self.on_edit_properties_activate(None)
File "/usr/lib/pymodules/python2.6/Alacarte/MainWindow.py", line 377, in
on_edit_properties_activate
self.editor._MenuEditor__addUndo([(file_type,
os.path.split(file_path)[1]),])
File "/usr/lib/pymodules/python2.6/Alacarte/MenuEditor.py", line 428, in
__addUndo
undo_path = util.getUniqueUndoFile(file_path)
File "/usr/lib/pymodules/python2.6/Alacarte/util.py", line 109, in
getUniqueUndoFile
filename, extension = os.path.split(filepath)[1].rsplit('.', 1)
ValueError: need more than 1 value to unpack
james@Lucid:~$ lsb_release -rd
Descript
[Desktop-packages] [Bug 1470640] Re: In Vivid Vervet, onscreen keyboard won't input to password/user fields
It's the bug in lightdm-gtk-greeter and it was fixed in 2.0.1. Use this PPA to get update for 15.04: https://launchpad.net/~lightdm-gtk-greeter-team/+archive/ubuntu/stable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1470640 Title: In Vivid Vervet, onscreen keyboard won't input to password/user fields Status in onboard package in Ubuntu: New Bug description: X/Ubuntu 15: Onboard keyboard works fine in desktop environments, but will not pass input to user/password slots at login/resume screen. Clicking with a mouse OR tapping on a touchscreen does not work. Subsequently, when using a regular keyboard, after trying with onscreen keyboard, you must click into the password field again before input from regular keyboard is accepted. Suspect that focus is not being properly returned/shifted to the text input field by the keyboard, and the field itself is losing programmatic focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1470640/+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 1398619] Re: No indicators displayed when systemd-sysv is installed
** Branch linked: lp:~kalgasnik/lightdm-gtk-greeter/pre2.0-bugfixes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1398619 Title: No indicators displayed when systemd-sysv is installed Status in lightdm-gtk-greeter package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Fix Released Status in xfce4-indicator-plugin package in Ubuntu: Fix Released Bug description: s/init/upstart/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm-gtk-greeter/+bug/1398619/+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 1393846] Re: Screen Lock shows wrong wallpaper
Can you post content of "/var/lib/AccountsService/users/" file? And what is your current wallpaper: color, gradient or file (post it too)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1393846 Title: Screen Lock shows wrong wallpaper Status in “lightdm” package in Ubuntu: New Bug description: Hi, after locking my screen the login screen displays the standard XFCE- Backgroung wallpaper. However, I am not using XFCE and I expect it to display either the standard wallpaper for the login screen or my personal wallpaper to be displayed. This is only one bug of a series of bugs concerning the screen lock. They are probably all related. I will provide the links to the bug reports later, until then you can find them in my personal profile. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Tue Nov 18 17:12:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-13 (673 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter allow-guest=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+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 1393846] Re: Screen Lock shows wrong wallpaper
AccountsService file: Background=/usr/share/xfce4/backdrops/xubuntu-wallpaper.png Lightdm uses this value as user's background at login screen. But AccountsService do not support color as "Background" value. When you change your background to black color the old value is not updated. And you will see your old wallpaper at login screen. Just remove this line or change your wallpaper to desired image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1393846 Title: Screen Lock shows wrong wallpaper Status in “lightdm” package in Ubuntu: New Bug description: Hi, after locking my screen the login screen displays the standard XFCE- Backgroung wallpaper. However, I am not using XFCE and I expect it to display either the standard wallpaper for the login screen or my personal wallpaper to be displayed. This is only one bug of a series of bugs concerning the screen lock. They are probably all related. I will provide the links to the bug reports later, until then you can find them in my personal profile. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Tue Nov 18 17:12:00 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-13 (673 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter allow-guest=true ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-09-14 (64 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1393846/+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 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
Since you are using gtk-greeter - can you test version from this PPA? https://code.launchpad.net/~kalgasnik/+archive/ubuntu/lightdm-gtk-greeter-background-transition -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+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
