| 2009-02-13 17:54:42 |
Martin Erik Werner |
bug |
|
|
added bug |
| 2009-02-13 18:41:05 |
Sebastien Bacher |
nautilus: status |
New |
Incomplete |
|
| 2009-02-13 18:41:05 |
Sebastien Bacher |
nautilus: assignee |
|
desktop-bugs |
|
| 2009-02-13 18:41:05 |
Sebastien Bacher |
nautilus: importance |
Undecided |
Low |
|
| 2009-02-13 18:41:05 |
Sebastien Bacher |
nautilus: statusexplanation |
|
thank you for your bug report, do you use the option to not display the background in nautilus? |
|
| 2009-02-13 19:19:13 |
Martin Erik Werner |
description |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
|
| 2009-02-13 19:36:23 |
Martin Erik Werner |
description |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}). I also don't see any desktop wallpaper, only solid colour.
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
|
| 2009-02-15 17:07:02 |
Martin Erik Werner |
description |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}). I also don't see any desktop wallpaper, only solid colour.
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
|
| 2009-02-16 22:14:26 |
Bernard |
description |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT). |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT).
This message is spammed to dmesg:
Ienorand: from dmesg: [ 42.636631] nautilus[3660]: segfault at 98a0008 ip b5d9755d sp b5d85fc0 error 4 in libbrasero-media.so.0.1.1[b5d87000+1e000]
Removing the package libbrasero-media0 stops the spawning nautilus sessions. Nautilus works as expected, too. |
|
| 2009-02-16 22:15:16 |
Bernard |
description |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT).
This message is spammed to dmesg:
Ienorand: from dmesg: [ 42.636631] nautilus[3660]: segfault at 98a0008 ip b5d9755d sp b5d85fc0 error 4 in libbrasero-media.so.0.1.1[b5d87000+1e000]
Removing the package libbrasero-media0 stops the spawning nautilus sessions. Nautilus works as expected, too. |
When I login nautilus is unable to launch, which results in an infinite spamming of "starting file manager" in the window list (they seem to reach an equillibrium at ~20 where they are created at the rate the close {presumably after failing to start and quitting similarly to manual launch below}).
If I launch nautilus from terminal I get this message:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Message did not receive a reply (timeout by message bus)
###
Followed after a moment by:
###
(nautilus:8776): Unique-DBus-WARNING **: Error while sending message: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
###
After the last message all "starting file manager" instances dissapear (or rather, stops being spawned, and closes one by one until window-list is empty). Whereupon they start spawning all over again, with exact same behaviour.
DBus is running:
###
mw@jaunty-virt:~$ ps -ef | grep dbus
106 2664 1 0 17:17 ? 00:00:14 /bin/dbus-daemon --system
mw 3423 3329 0 17:17 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3426 1 0 17:17 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager
mw 3427 1 1 17:17 ? 00:00:23 //bin/dbus-daemon --fork --print-pid 6 --print-address 9 --session
mw 13151 4656 0 17:43 pts/0 00:00:00 grep dbus
###
I can find no relevant entried in ~/var/log/daemon.log
I can find no nautilus-debug* crash files in ~/
nautilus show_desktop value in gconf is set to true
I've had odd things when the issue seemed to go away after I ran apt-get upgrade (which added several packages, none of which directly nautilus-related I think), and then after restart it only happened for ~10s after login, and then after shutdown and start it's back to original behaviour, but I'm not completely sure about circumstances there...
I've had comments suggesting it may be unrelated to nautilus itself.
Issue started after recent upgrade (~12 feb GMT)
Running Jaunty on vmware, fully upgraded as of now (13 feb GMT).
This message is spammed to dmesg:
[ 42.636631] nautilus[3660]: segfault at 98a0008 ip b5d9755d sp b5d85fc0 error 4 in libbrasero-media.so.0.1.1[b5d87000+1e000]
Removing the package libbrasero-media0 stops the spawning nautilus sessions. Nautilus works as expected, too. |
|
| 2009-02-16 22:27:00 |
Martin Erik Werner |
nautilus: bugtargetdisplayname |
nautilus (Ubuntu) |
brasero (Ubuntu) |
|
| 2009-02-16 22:27:00 |
Martin Erik Werner |
nautilus: bugtargetname |
nautilus (Ubuntu) |
brasero (Ubuntu) |
|
| 2009-02-16 22:27:00 |
Martin Erik Werner |
nautilus: statusexplanation |
thank you for your bug report, do you use the option to not display the background in nautilus? |
|
|
| 2009-02-16 22:27:00 |
Martin Erik Werner |
nautilus: title |
Bug #329146 in nautilus (Ubuntu): "nautilus unable to start on login" |
Bug #329146 in brasero (Ubuntu): "nautilus unable to start on login" |
|
| 2009-02-16 22:28:26 |
Martin Erik Werner |
brasero: status |
Incomplete |
New |
|
| 2009-02-16 22:34:14 |
Martin Erik Werner |
brasero: bugtargetdisplayname |
brasero (Ubuntu) |
nautilus (Ubuntu) |
|
| 2009-02-16 22:34:14 |
Martin Erik Werner |
brasero: bugtargetname |
brasero (Ubuntu) |
nautilus (Ubuntu) |
|
| 2009-02-16 22:34:14 |
Martin Erik Werner |
brasero: title |
Bug #329146 in brasero (Ubuntu): "nautilus unable to start on login" |
Bug #329146 in nautilus (Ubuntu): "nautilus unable to start on login" |
|
| 2009-02-16 22:34:46 |
Martin Erik Werner |
nautilus: status |
New |
Invalid |
|
| 2009-02-16 22:35:20 |
Martin Erik Werner |
bug |
|
|
assigned to brasero (Ubuntu) |
| 2009-02-19 18:25:35 |
Pedro Villavicencio |
brasero: status |
New |
Incomplete |
|
| 2009-02-19 18:25:35 |
Pedro Villavicencio |
brasero: importance |
Undecided |
Low |
|
| 2009-02-19 18:25:35 |
Pedro Villavicencio |
brasero: statusexplanation |
|
and what's the workaround? why is this a brasero issue? could you please elaborate? |
|
| 2009-02-19 19:28:58 |
Martin Erik Werner |
bug |
|
|
added attachment 'messages_log.txt' (messages_log.txt) |
| 2009-02-19 21:16:44 |
Martin Erik Werner |
bug |
|
|
added attachment 'New VM.vmx' (New VM.vmx) |
| 2009-02-19 21:17:11 |
Martin Erik Werner |
bug |
|
|
added attachment 'New VM.vmdk' (New VM.vmdk) |
| 2009-07-11 02:28:41 |
Martin Erik Werner |
brasero (Ubuntu): status |
Incomplete |
Invalid |
|
| 2010-05-10 13:28:49 |
Daisuke_Ido |
removed subscriber Daisuke_Ido |
|
|
|
