From: Camaleón on 21 Mar 2010 15:50 Hello, I have udpated -in one of my testing computers running Lenny/GNOME- Iceweasel package from backports (now featuring 3.5.8). So far so good :-) But I have noted that when launching the program from taskbar icon (associated command "iceweasel %u") Iceweasel opens fine but mouse cursor keeps the busy status (round ball) until a few secons, even though the program has been fully started. But if I launch the program from a GNOME terminal ("iceweasel") that does not happen, and cursor gets the right status (pointer) with no delay. Is someone seeing that behavior or it's just me? If yes, I could report it to the backport's guys. If not, something went wrong at my side and any hints would be great :-) Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/pan.2010.03.21.19.47.23(a)gmail.com
From: Liam O'Toole on 21 Mar 2010 16:20 On 2010-03-21, Camaleón <noelamac(a)gmail.com> wrote: > Hello, > > I have udpated -in one of my testing computers running Lenny/GNOME- > Iceweasel package from backports (now featuring 3.5.8). So far so good :-) > > But I have noted that when launching the program from taskbar icon > (associated command "iceweasel %u") Iceweasel opens fine but mouse cursor > keeps the busy status (round ball) until a few secons, even though the > program has been fully started. > > But if I launch the program from a GNOME terminal ("iceweasel") that does > not happen, and cursor gets the right status (pointer) with no delay. > > Is someone seeing that behavior or it's just me? > > If yes, I could report it to the backport's guys. If not, something went > wrong at my side and any hints would be great :-) > I see the same behaviour with iceweasel from backports. When you launch iceweasel from the menu or a panel icon then you get start-up notification as specified in the last line of the file /usr/share/applications/iceweasel.desktop. When you launch from a terminal, that is not the case. Still, I don't know the underlying reason why iceweasel displays the busy cursor for so long. Presumably some internal initialisation is taking longer than expected. But I'm convinced that that is still the case when launching from a terminal: it's just that we are not being made aware of the fact. -- Liam O'Toole Birmingham, United Kingdom -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/slrnhqcvf2.4kh.liam.p.otoole(a)dipsy.selfip.org
From: Camaleón on 21 Mar 2010 17:50 On Sun, 21 Mar 2010 20:13:22 +0000, Liam O'Toole wrote: > On 2010-03-21, Camaleón wrote: (...) >> Is someone seeing that behavior or it's just me? >> >> If yes, I could report it to the backport's guys. If not, something >> went wrong at my side and any hints would be great :-) >> >> > I see the same behaviour with iceweasel from backports. When you launch > iceweasel from the menu or a panel icon then you get start-up > notification as specified in the last line of the file > /usr/share/applications/iceweasel.desktop. When you launch from a > terminal, that is not the case. > > Still, I don't know the underlying reason why iceweasel displays the > busy cursor for so long. Presumably some internal initialisation is > taking longer than expected. But I'm convinced that that is still the > case when launching from a terminal: it's just that we are not being > made aware of the fact. Thanks for your feedback. I think I've discovered a very "dumb" trick. Just creating a new launcher seems to solve the problem. You can use the same options (command: iceweasel %u, description: Web browsing... etc.) Could you please check if it also works for you? Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/pan.2010.03.21.21.44.42(a)gmail.com
From: Liam O'Toole on 21 Mar 2010 18:10 On 2010-03-21, Camaleón <noelamac(a)gmail.com> wrote: > On Sun, 21 Mar 2010 20:13:22 +0000, Liam O'Toole wrote: > >> On 2010-03-21, Camaleón wrote: > > (...) > >>> Is someone seeing that behavior or it's just me? >>> >>> If yes, I could report it to the backport's guys. If not, something >>> went wrong at my side and any hints would be great :-) >>> >>> >> I see the same behaviour with iceweasel from backports. When you launch >> iceweasel from the menu or a panel icon then you get start-up >> notification as specified in the last line of the file >> /usr/share/applications/iceweasel.desktop. When you launch from a >> terminal, that is not the case. >> >> Still, I don't know the underlying reason why iceweasel displays the >> busy cursor for so long. Presumably some internal initialisation is >> taking longer than expected. But I'm convinced that that is still the >> case when launching from a terminal: it's just that we are not being >> made aware of the fact. > > Thanks for your feedback. I think I've discovered a very "dumb" trick. > > Just creating a new launcher seems to solve the problem. You can use the > same options (command: iceweasel %u, description: Web browsing... etc.) > > Could you please check if it also works for you? > Yes, creating a new, minimal, .desktop file solves the problem. Here is the one I used: [Desktop Entry] Encoding=UTF-8 Version=1.0 Type=Application Terminal=false Name[en_GB]=iceweasl Exec=/usr/bin/iceweasel Icon[en_GB]=iceweasel Name=iceweasl Icon=iceweasel The browser window popped up immmediately, without the busy cursor. I would be interested to learn which part of the official .desktop file is responsible for the behaviour you first observed. -- Liam O'Toole Birmingham, United Kingdom -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/slrnhqd67f.4kh.liam.p.otoole(a)dipsy.selfip.org
From: John A. Sullivan III on 22 Mar 2010 06:10
On Sun, 2010-03-21 at 22:08 +0000, Liam O'Toole wrote: > On 2010-03-21, Camaleón <noelamac(a)gmail.com> wrote: > > On Sun, 21 Mar 2010 20:13:22 +0000, Liam O'Toole wrote: > > > >> On 2010-03-21, Camaleón wrote: > > > > (...) > > > >>> Is someone seeing that behavior or it's just me? > >>> > >>> If yes, I could report it to the backport's guys. If not, something > >>> went wrong at my side and any hints would be great :-) > >>> > >>> > >> I see the same behaviour with iceweasel from backports. When you launch > >> iceweasel from the menu or a panel icon then you get start-up > >> notification as specified in the last line of the file > >> /usr/share/applications/iceweasel.desktop. When you launch from a > >> terminal, that is not the case. > >> > >> Still, I don't know the underlying reason why iceweasel displays the > >> busy cursor for so long. Presumably some internal initialisation is > >> taking longer than expected. But I'm convinced that that is still the > >> case when launching from a terminal: it's just that we are not being > >> made aware of the fact. > > > > Thanks for your feedback. I think I've discovered a very "dumb" trick. > > > > Just creating a new launcher seems to solve the problem. You can use the > > same options (command: iceweasel %u, description: Web browsing... etc.) > > > > Could you please check if it also works for you? > > > > Yes, creating a new, minimal, .desktop file solves the problem. Here is > the one I used: > > [Desktop Entry] > Encoding=UTF-8 > Version=1.0 > Type=Application > Terminal=false > Name[en_GB]=iceweasl > Exec=/usr/bin/iceweasel > Icon[en_GB]=iceweasel > Name=iceweasl > Icon=iceweasel > > The browser window popped up immmediately, without the busy cursor. > > I would be interested to learn which part of the official .desktop file > is responsible for the behaviour you first observed. <snip> We are seeing the same behavior and would very much like to solve this problem. I tracked down the iceweasel.desktop file to /usr/share/applications. I first commented out the non-language related items that did not appear in your .desktop file above. That did not fix it. I then removed all the language related entries except the default in case it was a bad language entry. That did not fix it. I then replaced the file with the one you give above. That did not fix it. Then I wondered if it was a location issue. So I placed your file in ~/Desktop so it showed up as a desktop icon rather than a menu icon. Alas that did not fix it either. At a loss for what to try next - John -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/1269251945.3491.4.camel(a)localhost |