[Bug 1087920] Re: gimp crashes after save as
This bug is also regsitrated as https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1048657 It is not solved there. I have the same problem. I am using Ubuntu 12.04 and Gimp 2.6.12 A new GIMP image can be save under a given name with save as. When I try to save an already named file under a new name with save as, GIMP crashes. The file is saved under the new name before crash, and can be opened again and can be edited. If I use save as, but do not change the name, no crash occurs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1087920 Title: gimp crashes after save as To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1087920/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1048657] Re: Ubuntu 12.04 / Gimp - Consistent crash after saving file
I have the same problem. I am using Ubuntu 12.04 and Gimp 2.6.12 A new GIMP image can be save under a given name with save as. When I try to save an already named file under a new name with save as, GIMP crashes. The fil is saved under the new name before crash, and can be opened again and can be edited. If I use save as, but do not change the name, no crash occurs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1048657 Title: Ubuntu 12.04 / Gimp - Consistent crash after saving file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1048657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1048657] Re: Ubuntu 12.04 / Gimp - Consistent crash after saving file
I just noticed, this bug is also registrated as https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1087920 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1048657 Title: Ubuntu 12.04 / Gimp - Consistent crash after saving file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1048657/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
Hi Bladud, I have again turned on nepomuk and shutdown. Started again and during the second shutdown, the command suggested by you, ps -wweo pid,state,args | grep nepomuk gave the following result (during shutdown fase, every 2 sec ps command was given, results from are given from the last one (about 34 sec. after the shutdown command)): 2049 S /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder 2094 S /usr/bin/nepomukserver 2099 S /usr/bin/nepomukservicestub nepomukstorage 2123 S /usr/bin/nepomukservicestub nepomukqueryservice 2124 S /usr/bin/nepomukservicestub nepomukfilewatch 2125 S /usr/bin/nepomukservicestub nepomukbackupsync 2126 S /usr/bin/nepomukservicestub nepomukfileindexer 2431 S grep nepomuk S /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder 2094 S /usr/bin/nepomukserver 2099 S /usr/bin/nepomukservicestub nepomukstorage 2123 S /usr/bin/nepomukservicestub nepomukqueryservice 2124 S /usr/bin/nepomukservicestub nepomukfilewatch 2125 S /usr/bin/nepomukservicestub nepomukbackupsync 2126 S /usr/bin/nepomukservicestub nepomukfileindexer 2431 S grep nepomuk My version of nepomuk is: kde-runtime-data 4:4.8.5-0ubuntu0.1 Success with finding the cause of the bug. Nelly -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
Answer to Bladud (#10 + #12) I have tried to run the command ps -el | grep nepomuk as long as possible after the shutdown command (given with the GUI logout button) using a BASH function giving that command every 2 sec and saving the results in a file. After 20-30 sec. the termninal window disappears and the function stops. I don't find differences in the result just before giving the logout command and during these seconds hanging. I have performed the test twice, once with the nepomuk functions working and programmed to start in the next logon, and once after I had prevented the starting of some nepomuk services at start-up (see #6). Surprisingly the results of these two tests differed slightly. The first test gave: 0 S 1000 2062 1987 0 80 0 - 32753 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2108 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2114 2108 2 99 - - 49593 poll_s R 00:00:00 nepomukservices 0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices 0 S 1000 2199 2108 0 99 - - 32401 futex_ R 00:00:00 nepomukservices 0 S 1000 2200 2108 0 99 - - 26909 poll_s R 00:00:00 nepomukservices 0 S 1000 2201 2108 0 99 - - 25321 poll_s R 00:00:00 nepomukservices S 1000 2062 1987 0 80 0 - 32753 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2108 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2114 2108 2 99 - - 49593 poll_s R 00:00:00 nepomukservices 0 D 1000 2198 2108 7 99 - - 32215 sleep_ R 00:00:02 nepomukservices 0 S 1000 2199 2108 0 99 - - 32401 futex_ R 00:00:00 nepomukservices 0 S 1000 2200 2108 0 99 - - 26909 poll_s R 00:00:00 nepomukservices 0 S 1000 2201 2108 0 99 - - 25321 poll_s R 00:00:00 nepomukservices and the second test: 0 S 1000 2052 1989 0 80 0 - 33984 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2101 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2106 2101 0 99 - - 54348 poll_s R 00:00:00 nepomukservices 0 S 1000 2126 2101 0 99 - - 32400 futex_ R 00:00:00 nepomukservices 0 S 1000 2127 2101 0 99 - - 26945 poll_s R 00:00:00 nepomukservices 0 S 1000 2128 2101 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 0 S 1000 2129 2101 0 99 - - 32536 poll_s R 00:00:03 nepomukservices S 1000 2052 1989 0 80 0 - 33984 poll_s R 00:00:00 akonadi_nepomuk 0 S 1000 2101 1 0 80 0 - 17073 poll_s R 00:00:00 nepomukserver 0 S 1000 2106 2101 0 99 - - 54348 poll_s R 00:00:00 nepomukservices 0 S 1000 2126 2101 0 99 - - 32400 futex_ R 00:00:00 nepomukservices 0 S 1000 2127 2101 0 99 - - 26945 poll_s R 00:00:00 nepomukservices 0 S 1000 2128 2101 0 99 - - 25321 poll_s R 00:00:00 nepomukservices 0 S 1000 2129 2101 0 99 - - 32536 poll_s R 00:00:03 nepomukservices Hope this helps. What happens during the rest of the shutdown cannot be tested easily because the computer is no longer accessible. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
Answer to Bladud (#10) I first tried ps -e0 stat | grep nepomuk during normal run-time to see what kind of results I might expect. It did not work. ps -el | grep nepomuk resulted in: 0 S 1000 2158 1 0 80 0 - 14441 poll_s ?00:00:00 nepomukserver 0 S 1000 3467 3344 0 80 0 - 32744 poll_s ?00:00:00 akonadi_nepomuk 0 S 1000 3520 1 0 80 0 - 14441 poll_s ?00:00:00 nepomukserver and ps -eF | grep nepomuk resulted in: nelly 2158 1 0 14441 8700 0 10:42 ?00:00:00 /usr/bin/nepomukserver nelly 3467 3344 0 32744 26304 0 12:22 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder nelly 3520 1 0 14441 8700 1 12:23 ?00:00:00 /usr/bin/nepomukserver nelly 3810 3723 0 1103 832 0 13:20 pts/000:00:00 grep --color=auto nepomuk Is either of these the kind of output you are looking for? Which one? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
nepomuk processes running in situation with good shutdown (after adding the lines to ~/.kde/share/config/nepomukserverrc as described in my message of feb 11 and deleting /usr/share/autostart/nepomukcontroller.desktop) nelly 2066 1862 0 09:37 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder nelly 2098 1 0 09:37 ?00:00:00 /usr/bin/nepomukserver nelly 2920 2864 0 10:01 pts/000:00:00 grep --color=auto nepomuk I have no NFS system running (rpcinfo not installed, no file /etc/exports) I have deleted the extra lines in ~/.kde/share/config/nepomukserverrc and put the nepomukcontroller.desktop again in the map /usr/share/autostart/. Shutdown was OK (file appears only affect the system after a fresh start-up) Now nepomuk processes running are: nelly 2083 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder nelly 2132 1 0 10:28 ?00:00:00 /usr/bin/nepomukserver nelly 2139 2132 0 10:28 ?00:00:00 /usr/bin/nepomukservicestub nepomukstorage nelly 2157 2132 2 10:28 ?00:00:04 /usr/bin/nepomukservicestub nepomukfilewatch nelly 2158 2132 0 10:28 ?00:00:00 /usr/bin/nepomukservicestub nepomukfileindexer nelly 2159 2132 0 10:28 ?00:00:00 /usr/bin/nepomukservicestub nepomukbackupsync nelly 2160 2132 0 10:28 ?00:00:00 /usr/bin/nepomukservicestub nepomukqueryservice nelly 2392 2338 0 10:31 pts/000:00:00 grep --color=auto nepomuk ( the akonadi processes running were: nelly 2007 1 0 10:27 ?00:00:00 /usr/bin/akonadi_control nelly 2009 2007 0 10:27 ?00:00:00 akonadiserver nelly 2011 2009 0 10:27 ?00:00:00 /usr/sbin/mysqld --defaults-file=/home/nelly/.local/share/akonadi/mysql.conf --datadir=/home/nelly/.local/share/akonadi/db_data/ --socket=/home/nelly/.local/share/akonadi/socket-ecostat5/mysql.socket nelly 2075 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_akonotes_resource akonadi_akonotes_resource_0 nelly 2076 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_contacts_resource akonadi_contacts_resource_0 nelly 2077 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_ical_resource akonadi_ical_resource_0 nelly 2078 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource akonadi_kalarm_resource_0 nelly 2079 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource akonadi_kalarm_resource_1 nelly 2080 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_kalarm_resource akonadi_kalarm_resource_2 nelly 2081 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_agent_launcher akonadi_maildir_resource akonadi_maildir_resource_0 nelly 2082 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_maildispatcher_agent --identifier akonadi_maildispatcher_agent nelly 2083 2007 0 10:28 ?00:00:00 /usr/bin/akonadi_nepomuk_feeder --identifier akonadi_nepomuk_feeder nelly 2465 2338 0 10:37 pts/000:00:00 grep --color=auto akon The nepomukserverrc file had no effect omn the akonadi processes running) I added again the extra lines in ~/.kde/share/config/nepomukserverrc and removed the nepomukcontroller.desktop from in the map /usr/share/autostart/. Shutdown was slow (all nepomuk processes were still running) and the pop-up stating that an unknown process was still running appeared again. After this restart the shutdown was OK again (within a few seconds). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1053783] Re: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info.
I also have this bug. I use KAlarm and my computer with Ubuntu 12.04 (Gnome desktop) took several minutes to shutdown. Link http://ubuntuforums.org/showthread.php?t=1764048 gave me the hint how to solve this problem. This link contains methods to prevent te starting up of nepomuk and akonadi in 3 steps. If you don't want to use KAlarm, it might be safe to apply all three steps. However, doing so, KAlarm could not be used. It asked to start-up akonadi first. So I tried what would happen if I only used the two steps preventing the (complete) start-up of nepomuk, and that worked great. KAlarm works and Ubuntu 12.04 shuts down within a few seconds. The steps to apply are: 1. Add the following lines to ~/.kde/share/config/nepomukserverrc (and their sections if they don't exist) (change the value from true to false if they do exist and are set on true; [Basic Settings] Start Nepomuk=false [Service-nepomukmigration1] autostart=false [Service-nepomukstrigiservice] autostart=false 2. Remove the file /usr/share/autostart/nepomukcontroller.desktop, if it exists. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1053783 Title: Ubuntu 12.04 - Stalled shutdown after having had KAlarm opened; with package info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1053783/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
