Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
gdm dies after l
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Changed in: gdm
Status: New => Invalid
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
This seems to be NO longer a problem for a system I recently installed
running on amd64 arch. So I guess the problem has resolved itself.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a membe
** Attachment added: "syslog messages from gdm (I enabled debug in gdm.conf)"
http://librarian.launchpad.net/5607823/syslog-gdm-messages
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: ".xsession-errors file logged in user as kde desktop"
http://librarian.launchpad.net/5607833/xsession-error-where-gdm-stop-listening-to-xdmcp-after-logging-into-kde
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
deskt
Thank you for your bug. Opening an upstream bug would be nice, they know
the code better and would probably have some idea on the problem. The
desktop team has lot to do and that configuration is not a standard one,
it's likely that nobody from Ubuntu will look at that bug soon
** Changed in: gdm
that's not likely to be due to a distribution patch, that's probably an
upstream bug then. gdm should work fine with any environment, not only
GNOME
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Seems to me that this is the same problem as bug #71924.
Please confirm.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
I have exactly the same situation (GDM running KDE over XDMCP on Ubuntu
6.06 with all updates applied, as of 21 March 2007) and GDM crashes
every time a remote user logs out from KDE. This doesn't happen with
Gnome or XFCE. I have to run sudo /etc/init.d/gdm restart to get it back
again.
Afraid I
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
gdm dies after l
This seems to be NO longer a problem for a system I recently installed
running on amd64 arch. So I guess the problem has resolved itself.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a membe
** Changed in: gdm
Status: New => Invalid
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
I have exactly the same situation (GDM running KDE over XDMCP on Ubuntu
6.06 with all updates applied, as of 21 March 2007) and GDM crashes
every time a remote user logs out from KDE. This doesn't happen with
Gnome or XFCE. I have to run sudo /etc/init.d/gdm restart to get it back
again.
Afraid I
** Attachment added: "syslog messages from gdm (I enabled debug in gdm.conf)"
http://librarian.launchpad.net/5607823/syslog-gdm-messages
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: ".xsession-errors file logged in user as kde desktop"
http://librarian.launchpad.net/5607833/xsession-error-where-gdm-stop-listening-to-xdmcp-after-logging-into-kde
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
deskt
Thank you for your bug. Opening an upstream bug would be nice, they know
the code better and would probably have some idea on the problem. The
desktop team has lot to do and that configuration is not a standard one,
it's likely that nobody from Ubuntu will look at that bug soon
** Changed in: gdm
that's not likely to be due to a distribution patch, that's probably an
upstream bug then. gdm should work fine with any environment, not only
GNOME
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Seems to me that this is the same problem as bug #71924.
Please confirm.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
This seems to be NO longer a problem for a system I recently installed
running on amd64 arch. So I guess the problem has resolved itself.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a membe
** Changed in: gdm
Status: New => Invalid
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
gdm dies after l
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Attachment added: "syslog messages from gdm (I enabled debug in gdm.conf)"
http://librarian.launchpad.net/5607823/syslog-gdm-messages
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: ".xsession-errors file logged in user as kde desktop"
http://librarian.launchpad.net/5607833/xsession-error-where-gdm-stop-listening-to-xdmcp-after-logging-into-kde
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
deskt
Thank you for your bug. Opening an upstream bug would be nice, they know
the code better and would probably have some idea on the problem. The
desktop team has lot to do and that configuration is not a standard one,
it's likely that nobody from Ubuntu will look at that bug soon
** Changed in: gdm
that's not likely to be due to a distribution patch, that's probably an
upstream bug then. gdm should work fine with any environment, not only
GNOME
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ub
I have exactly the same situation (GDM running KDE over XDMCP on Ubuntu
6.06 with all updates applied, as of 21 March 2007) and GDM crashes
every time a remote user logs out from KDE. This doesn't happen with
Gnome or XFCE. I have to run sudo /etc/init.d/gdm restart to get it back
again.
Afraid I
Seems to me that this is the same problem as bug #71924.
Please confirm.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
This seems to be NO longer a problem for a system I recently installed
running on amd64 arch. So I guess the problem has resolved itself.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a membe
** Changed in: gdm
Status: New => Invalid
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
gdm dies after l
Seems to me that this is the same problem as bug #71924.
Please confirm.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
I have exactly the same situation (GDM running KDE over XDMCP on Ubuntu
6.06 with all updates applied, as of 21 March 2007) and GDM crashes
every time a remote user logs out from KDE. This doesn't happen with
Gnome or XFCE. I have to run sudo /etc/init.d/gdm restart to get it back
again.
Afraid I
** Attachment added: "syslog messages from gdm (I enabled debug in gdm.conf)"
http://librarian.launchpad.net/5607823/syslog-gdm-messages
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: ".xsession-errors file logged in user as kde desktop"
http://librarian.launchpad.net/5607833/xsession-error-where-gdm-stop-listening-to-xdmcp-after-logging-into-kde
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
deskt
Thank you for your bug. Opening an upstream bug would be nice, they know
the code better and would probably have some idea on the problem. The
desktop team has lot to do and that configuration is not a standard one,
it's likely that nobody from Ubuntu will look at that bug soon
** Changed in: gdm
that's not likely to be due to a distribution patch, that's probably an
upstream bug then. gdm should work fine with any environment, not only
GNOME
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ub
** Attachment added: "syslog messages from gdm (I enabled debug in gdm.conf)"
http://librarian.launchpad.net/5607823/syslog-gdm-messages
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: ".xsession-errors file logged in user as kde desktop"
http://librarian.launchpad.net/5607833/xsession-error-where-gdm-stop-listening-to-xdmcp-after-logging-into-kde
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
deskt
Thank you for your bug. Opening an upstream bug would be nice, they know
the code better and would probably have some idea on the problem. The
desktop team has lot to do and that configuration is not a standard one,
it's likely that nobody from Ubuntu will look at that bug soon
** Changed in: gdm
that's not likely to be due to a distribution patch, that's probably an
upstream bug then. gdm should work fine with any environment, not only
GNOME
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
gdm dies after l
This seems to be NO longer a problem for a system I recently installed
running on amd64 arch. So I guess the problem has resolved itself.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a membe
** Changed in: gdm
Status: New => Invalid
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
Seems to me that this is the same problem as bug #71924.
Please confirm.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
I have exactly the same situation (GDM running KDE over XDMCP on Ubuntu
6.06 with all updates applied, as of 21 March 2007) and GDM crashes
every time a remote user logs out from KDE. This doesn't happen with
Gnome or XFCE. I have to run sudo /etc/init.d/gdm restart to get it back
again.
Afraid I
** Attachment added: "syslog messages from gdm (I enabled debug in gdm.conf)"
http://librarian.launchpad.net/5607823/syslog-gdm-messages
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
** Attachment added: ".xsession-errors file logged in user as kde desktop"
http://librarian.launchpad.net/5607833/xsession-error-where-gdm-stop-listening-to-xdmcp-after-logging-into-kde
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
deskt
Thank you for your bug. Opening an upstream bug would be nice, they know
the code better and would probably have some idea on the problem. The
desktop team has lot to do and that configuration is not a standard one,
it's likely that nobody from Ubuntu will look at that bug soon
** Changed in: gdm
that's not likely to be due to a distribution patch, that's probably an
upstream bug then. gdm should work fine with any environment, not only
GNOME
--
gdm dies after logging out after using kde desktop (dapper)
https://launchpad.net/bugs/78113
--
desktop-bugs mailing list
desktop-bugs@lists.ub
Seems to me that this is the same problem as bug #71924.
Please confirm.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-b
I have exactly the same situation (GDM running KDE over XDMCP on Ubuntu
6.06 with all updates applied, as of 21 March 2007) and GDM crashes
every time a remote user logs out from KDE. This doesn't happen with
Gnome or XFCE. I have to run sudo /etc/init.d/gdm restart to get it back
again.
Afraid I
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Hardy Heron. It would help us greatly if you could
test with it so we can work
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.
--
gdm dies after l
This seems to be NO longer a problem for a system I recently installed
running on amd64 arch. So I guess the problem has resolved itself.
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a membe
** Changed in: gdm
Status: New => Invalid
--
gdm dies after logging out after using kde desktop (dapper)
https://bugs.launchpad.net/bugs/78113
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop
Jorge Castro wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in ad
Sebastien Bacher wrote:
> Thank you for your bug. Opening an upstream bug would be nice, they know
> the code better and would probably have some idea on the problem. The
> desktop team has lot to do and that configuration is not a standard one,
> it's likely that nobody from Ubuntu will look at th
stkas wrote:
> Seems to me that this is the same problem as bug #71924.
> Please confirm.
>
>
Most likely it's same albeit #71924 is cluttered with other details.
I have not confirmed that it occurs on feisty and probably won't have
time to
confirm that in the near future due to time constraint
Jorge Castro wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in ad
Sebastien Bacher wrote:
> Thank you for your bug. Opening an upstream bug would be nice, they know
> the code better and would probably have some idea on the problem. The
> desktop team has lot to do and that configuration is not a standard one,
> it's likely that nobody from Ubuntu will look at th
stkas wrote:
> Seems to me that this is the same problem as bug #71924.
> Please confirm.
>
>
Most likely it's same albeit #71924 is cluttered with other details.
I have not confirmed that it occurs on feisty and probably won't have
time to
confirm that in the near future due to time constraint
Jorge Castro wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in ad
Sebastien Bacher wrote:
> Thank you for your bug. Opening an upstream bug would be nice, they know
> the code better and would probably have some idea on the problem. The
> desktop team has lot to do and that configuration is not a standard one,
> it's likely that nobody from Ubuntu will look at th
stkas wrote:
> Seems to me that this is the same problem as bug #71924.
> Please confirm.
>
>
Most likely it's same albeit #71924 is cluttered with other details.
I have not confirmed that it occurs on feisty and probably won't have
time to
confirm that in the near future due to time constraint
Jorge Castro wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in ad
stkas wrote:
> Seems to me that this is the same problem as bug #71924.
> Please confirm.
>
>
Most likely it's same albeit #71924 is cluttered with other details.
I have not confirmed that it occurs on feisty and probably won't have
time to
confirm that in the near future due to time constraint
Sebastien Bacher wrote:
> Thank you for your bug. Opening an upstream bug would be nice, they know
> the code better and would probably have some idea on the problem. The
> desktop team has lot to do and that configuration is not a standard one,
> it's likely that nobody from Ubuntu will look at th
Sebastien Bacher wrote:
> Thank you for your bug. Opening an upstream bug would be nice, they know
> the code better and would probably have some idea on the problem. The
> desktop team has lot to do and that configuration is not a standard one,
> it's likely that nobody from Ubuntu will look at th
Jorge Castro wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in ad
stkas wrote:
> Seems to me that this is the same problem as bug #71924.
> Please confirm.
>
>
Most likely it's same albeit #71924 is cluttered with other details.
I have not confirmed that it occurs on feisty and probably won't have
time to
confirm that in the near future due to time constraint
Sebastien Bacher wrote:
> Thank you for your bug. Opening an upstream bug would be nice, they know
> the code better and would probably have some idea on the problem. The
> desktop team has lot to do and that configuration is not a standard one,
> it's likely that nobody from Ubuntu will look at th
stkas wrote:
> Seems to me that this is the same problem as bug #71924.
> Please confirm.
>
>
Most likely it's same albeit #71924 is cluttered with other details.
I have not confirmed that it occurs on feisty and probably won't have
time to
confirm that in the near future due to time constraint
Jorge Castro wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. You reported this bug a while ago and there hasn't been
> any activity in it recently. We were wondering is this still an issue
> for you? Can you try with latest Ubuntu release? Thanks in ad
84 matches
Mail list logo