panel disappear when switch to netbook mode

Bug #338517 reported by perriman
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
desktop-switcher
Won't Fix
Undecided
Unassigned
desktop-switcher (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I have installed desktop-switcher on intrepid. I change to the classic mode and then go back to the netbook mode. When I go back, the top panel has disappear!

If I open a terminal and execute "nohub gnome-panel &" the panel come back but when I logout and login again it doesn't start.

I have tried to save the session but I have not luck...

I attach my .xsession-errors log, perhaps it can help

Thanks!!

Tags: ubuntu-unr
Revision history for this message
perriman (chuchiperriman) wrote :
Revision history for this message
Javier Collado (javier.collado) wrote :

On jaunty, using desktop-switcher 0.4.3ubuntu1, I've had the very same problem. In addition to this, when the gnome-panel has been launched the application icons aren't being added to the panel and the windows size cannot be controlled.

If you want me to attach any kind of information, just let me know. Thanks.

Revision history for this message
Neil J. Patel (njpatel) wrote :

Thanks for reporting this bug. Could you please use gconf-editor, and check the contents of the /desktop/gnome/session/required_components_list, and list them here? I'm wondering if "panel" is missing from the list.

Changed in desktop-switcher:
status: New → Triaged
Revision history for this message
Javier Collado (javier.collado) wrote :

Hello,

The contents of /desktop/gnome/session/required_components_list in my netbook is the following:
filemanager: nautilus
panel: gnome-panel
windowmanager: gnomewm

I've tried again to switch from classic to netbook mode and the following error has been displayed:
"An error ocurred while loading or saving configuration information for netbook-launcher. Some of your configuration settings may not work properly"

and in the details:
"Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://project.gnome.org/gconf/ for information. (Details - 1: Could not send message to gconf dameon: Message did not receive a reply (timeout by message bus))"

Does this error message provide any useful information to fix the problem?

Best regards,
    Javier

Revision history for this message
perriman (chuchiperriman) wrote :

I have the same data but windowmanager is gnome-wm instead of gnomewm.

Revision history for this message
mattmill30 (mattmill30) wrote :

I also have this problem.

Exactly the same as Javier.

After switching to classic and back to NBR.

I've run gnome-session-properties and added gnome-panel.

However the panel holds the classic layout, not the remix layout.

Also, I had to add metacity to gnome-session-properties as this wasn't loading either

Thanks,

Matthew Millar

Revision history for this message
Neil J. Patel (njpatel) wrote :

The latest desktop-switcher in Jaunty should fix the issue of the panel and window-manager being removed from required_components.

For your current set-up, I recommend switching to netbook-mode using desktop switcher (no need if your already on it) and then running:

gconftool-2 --recursive-unset /apps/panel

then restarting. This should reset your panel layout to the default layout when UNR is installed. Then, before using desktop-switcher again, you MUST:

rm -rf ~/.config/desktop-switcher

After that, you should be able to use desktop-switcher without random things happening. I would really appreciate testing this as the hard-freeze for Jaunty is fast-approaching, and this should be fixed by then. Thanks everyone for taking the time to report and comment on this bug.

Changed in desktop-switcher:
status: Triaged → Confirmed
Revision history for this message
Javier Collado (javier.collado) wrote :

Hello,

Using desktop-switcher 0.4.3-0ubuntu1 everything seemed to work fine when switching between the two modes. However, when trying several times, I got the same error I reported in my previous comment (message bus timeout).

After that, in classic mode the windows are still maximized and have no decoration and maximus process is still running. If maximus is killed, then classic behaviour is fine.

No problem found in netbook mode.

Best regards,
    Javier

Revision history for this message
Tommy Trussell (tommy-trussell) wrote :

Installed Ubuntu Jaunty 9.04 NBR on an Asus EeePC 900. Install went great, but at some point I used desktop-switcher to switch from NBR to regular desktop and when I tried to log back in to that account, just got desktop, no top panel, no windows. When I was able to get a window open there was no title bar, no controls. I tried deleting all the hidden files that seemed relevant in the home directory and I was able to make it better -- I think something in ~/.config was the show stopper.

I just reinstalled from scratch and am looking at the comments above... I'm wondering if the updated desktop-switcher didn't make it into Jaunty. The current behavior I am seeing is especially bad, as it renders the desktop unusable.

Revision history for this message
Javier Collado (javier.collado) wrote :

Hello,

Yes, desktop-switcher 0.4.4-0ubuntu1 still fails on a dell mini9: after switching several times the gnome-panel isn't displayed in the classic mode.

Best regards,
    Javier

Revision history for this message
Paul Larson (pwlars) wrote :

Is this not a dup of bug #349519?

Revision history for this message
Tommy Trussell (tommy-trussell) wrote :

I agree my situation closely matches bug #349519 (though I can't speak for the originator of THIS bug). I will try working through the suggestions in that report when I'm back on the affected machine.

Revision history for this message
Paul Larson (pwlars) wrote :

This bug has been moved to Ubuntu distribution.

Changed in desktop-switcher (Ubuntu):
status: New → Confirmed
Changed in desktop-switcher:
status: Confirmed → Won't Fix
tags: added: ubuntu-unr
Revision history for this message
Paul Larson (pwlars) wrote :

I believe this almost certainly has to be a dup of bug #349519. If you feel that this is not the case, please feel free to un-dup it and explain further how it is different.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.