Re: [Desktop-packages] [Bug 1407015] Re: Both nemo and nautilus chrash when opening a nfs share
Hi. As to Unity, I will try, but this will require some time, because in the meanwhile I rearranged the root folder of the crashing share, so that the items are now much less (142), and the problem disappeared. Nemo nor Nautilus do not crash anymore. This tell us that in some way this bug is tied to the number of items, which is a problem only for NFS shares. I can add TO THE ROOT some dummy item (i.e; empty files to reproduce the problem), then trying first using a regular live 14.04 from a pen. This bug is very crazy, I cannot figure out where the problem should be located. I will keep you up to date. As to the other minor bugs, they are in any case tied to gnome (gnome-contacts and main menu). Where I have to file a bug report? Regards. Il 03/01/2015 11:21, Alberts Muktupāvels ha scritto: Please try with Unity. I have no idea how much you have removed nor how to restore them. You can try to install ubuntu-desktop, but not sure if it will reinstall unity. You opened bug for gnome-panel... If it will crash in Unity than it is not bug in gnome-panel, but in other pacakge. And please open new bug report for other problems. I don't know anyting about gnome-contacts. -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`º°¤ø,¸ Lorenzo Seno ~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1407015 Title: Both nemo and nautilus chrash when opening a nfs share Status in gnome-panel package in Ubuntu: New Bug description: I have a computer with ubuntu 14.04 gnome flashback 64bit. It was a fresh install, and it is currently updated. I use a NAS with 4 shared folders via NFS. When trying to open one - and only one - of them using both nautilus or nemo, both nautilus and nemo crash immediately, after a few seconds, while the remaining shares are instead OK. Apport seems unable to show details, and crashes itself. Crash erases any icon from the desktop. Everything is nevertheless correctly restored disconnecting the user then reconnecting logging on. Same behavior using both Compitz and Metacity. I can open the crashing share using terminal or midnight commander without any problem. I can see files/Folders, delete, move, copy, etc. No troubles using nemo or nautilus on local folders (e.g. opening /usr/bin, which is a populated folder). The crashing share is correctly opened by a different computer using Ubuntu 12.04 32bit Gnome fallback session and Nautilus. No troubles at all. The lone difference I can observe between the crashing share and the other three is that the crashing share shows a lot of items (filesdirectories) in its root, of the order of few hundreds, while the remaining three shares shows only some dozen of items (I can exactly count them if necessary). That's all folks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1407015/+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 1407015] Re: Both nemo and nautilus chrash when opening a nfs share
If default session means Unity, I can't try, because I removed Unity from both my 14.04 64 bit and 12.04 32 bit Ubuntu computers. I can reinstall it, if necessary, and try. In this case, please provide some instructions (apt command line). Thank you and regards. And happy new year, of course. PS: BTW there is another off-topic trouble (bug) in my 14.04 installation: gnome-contacts is unable to show my google contacts. Sometimes I get the request to re-authorize the access to my google account. Even doing successfully so, contacts do not appear. Some sparse problems also with main menu handling, when using custom icons and commands. Using menu libre solve this problem, but the intermix of alacarte and menu libre splits categories (I have double categories in my menu). So, from my point of view, 14.04 is quite buggy, and this prevents me from upgrading my 12.04 version. Il 02/01/2015 10:45, Alberts Muktupāvels ha scritto: Does it crash if you use ubuntu default session? -- ¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸¸,ø¤º°`º°¤ø,¸ Lorenzo Seno ~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~°~o_o~ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1407015 Title: Both nemo and nautilus chrash when opening a nfs share Status in gnome-panel package in Ubuntu: New Bug description: I have a computer with ubuntu 14.04 gnome flashback 64bit. It was a fresh install, and it is currently updated. I use a NAS with 4 shared folders via NFS. When trying to open one - and only one - of them using both nautilus or nemo, both nautilus and nemo crash immediately, after a few seconds, while the remaining shares are instead OK. Apport seems unable to show details, and crashes itself. Crash erases any icon from the desktop. Everything is nevertheless correctly restored disconnecting the user then reconnecting logging on. Same behavior using both Compitz and Metacity. I can open the crashing share using terminal or midnight commander without any problem. I can see files/Folders, delete, move, copy, etc. No troubles using nemo or nautilus on local folders (e.g. opening /usr/bin, which is a populated folder). The crashing share is correctly opened by a different computer using Ubuntu 12.04 32bit Gnome fallback session and Nautilus. No troubles at all. The lone difference I can observe between the crashing share and the other three is that the crashing share shows a lot of items (filesdirectories) in its root, of the order of few hundreds, while the remaining three shares shows only some dozen of items (I can exactly count them if necessary). That's all folks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1407015/+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 1407015] [NEW] Both nemo and nautilus chrash when opening a nfs share
Public bug reported: I have a computer with ubuntu 14.04 gnome flashback 64bit. It was a fresh install, and it is currently updated. I use a NAS with 4 shared folders via NFS. When trying to open one - and only one - of them using both nautilus or nemo, both nautilus and nemo crash immediately, after a few seconds, while the remaining shares are instead OK. Apport seems unable to show details, and crashes itself. Crash erases any icon from the desktop. Everything is nevertheless correctly restored disconnecting the user then reconnecting logging on. Same behavior using both Compitz and Metacity. I can open the crashing share using terminal or midnight commander without any problem. I can see files/Folders, delete, move, copy, etc. No troubles using nemo or nautilus on local folders (e.g. opening /usr/bin, which is a populated folder). The crashing share is correctly opened by a different computer using Ubuntu 12.04 32bit Gnome fallback session and Nautilus. No troubles at all. The lone difference I can observe between the crashing share and the other three is that the crashing share shows a lot of items (filesdirectories) in its root, of the order of few hundreds, while the remaining three shares shows only some dozen of items (I can exactly count them if necessary). That's all folks. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: crash nautilus nemo -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1407015 Title: Both nemo and nautilus chrash when opening a nfs share Status in gnome-panel package in Ubuntu: New Bug description: I have a computer with ubuntu 14.04 gnome flashback 64bit. It was a fresh install, and it is currently updated. I use a NAS with 4 shared folders via NFS. When trying to open one - and only one - of them using both nautilus or nemo, both nautilus and nemo crash immediately, after a few seconds, while the remaining shares are instead OK. Apport seems unable to show details, and crashes itself. Crash erases any icon from the desktop. Everything is nevertheless correctly restored disconnecting the user then reconnecting logging on. Same behavior using both Compitz and Metacity. I can open the crashing share using terminal or midnight commander without any problem. I can see files/Folders, delete, move, copy, etc. No troubles using nemo or nautilus on local folders (e.g. opening /usr/bin, which is a populated folder). The crashing share is correctly opened by a different computer using Ubuntu 12.04 32bit Gnome fallback session and Nautilus. No troubles at all. The lone difference I can observe between the crashing share and the other three is that the crashing share shows a lot of items (filesdirectories) in its root, of the order of few hundreds, while the remaining three shares shows only some dozen of items (I can exactly count them if necessary). That's all folks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1407015/+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 1407015] Re: Both nemo and nautilus chrash when opening a nfs share
Some further information. Opening the crashing share via SMB intead of NFS allows correcly see files, navigate, etc. everything is OK. This happens using both Nemo and Nautilus. (this is for me a workaround). The number of items in the root of the crashing share is exactly 621, files directories (mainly files). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1407015 Title: Both nemo and nautilus chrash when opening a nfs share Status in gnome-panel package in Ubuntu: New Bug description: I have a computer with ubuntu 14.04 gnome flashback 64bit. It was a fresh install, and it is currently updated. I use a NAS with 4 shared folders via NFS. When trying to open one - and only one - of them using both nautilus or nemo, both nautilus and nemo crash immediately, after a few seconds, while the remaining shares are instead OK. Apport seems unable to show details, and crashes itself. Crash erases any icon from the desktop. Everything is nevertheless correctly restored disconnecting the user then reconnecting logging on. Same behavior using both Compitz and Metacity. I can open the crashing share using terminal or midnight commander without any problem. I can see files/Folders, delete, move, copy, etc. No troubles using nemo or nautilus on local folders (e.g. opening /usr/bin, which is a populated folder). The crashing share is correctly opened by a different computer using Ubuntu 12.04 32bit Gnome fallback session and Nautilus. No troubles at all. The lone difference I can observe between the crashing share and the other three is that the crashing share shows a lot of items (filesdirectories) in its root, of the order of few hundreds, while the remaining three shares shows only some dozen of items (I can exactly count them if necessary). That's all folks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1407015/+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 1029289] Re: Need to authorize my google account each time I boot the computer
Hi, I'm posting my personal case history hoping this can be useful. I had two laptops both running Ubuntu12.04 (Gnome, w/o Unity). One of them - Acer - equipped by 32 bits version, the other - Asus - whith 64 bits version. No troubles with both even when authenticating at the same time to my google account. Both never asked me for authorization. In both laptop I used the contact application to keep my google contacts. Everything was fine. Now I upgraded Asus to 14.04 (64Bit, of course). This kept about a couple oh hours then everithing was fine, with the exception of a few details I solved in the next hours. Now the situation is as follows: 32 Bits 12.04 Acer everithing is fine, never asks for auth to my google account. Contacts into the application are fine as ever. 64 Bits 14.04 Asus asks me auth every time I log on, and my contacts are empty, even after hours from logon. Google account appears in the menu and it is correctly chosen as contacs source (Rubrica in italian). This situation is up to date at 30/08/2014. Both Ubuntu installations updated and upgraded. Hoping this can help developers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Confirmed Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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
