[Bug 1167028] Re: kdeinit4 segmentation fault

2013-11-23 Thread Harald Sitter
Hi there! Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct

[Bug 1167028] Re: kdeinit4 segmentation fault

2013-07-21 Thread Scott Stehno
I used bleachbit and gtkorphan to remove ophan packages. The system has not crashed so far. I have restarted and seems to free of crashes so far. I think maybe a good cleaning was in order. I had upgraded a lot of packages and had not cleaned the system in about 8 months. Might help others to try

[Bug 1167028] Re: kdeinit4 segmentation fault

2013-05-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kscreen (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1167028 Title:

[Bug 1167028] Re: kdeinit4 segmentation fault

2013-05-02 Thread Harald Sitter
** Package changed: kde4libs (Ubuntu) = kscreen (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde4libs in Ubuntu. https://bugs.launchpad.net/bugs/1167028 Title: kdeinit4 segmentation fault To manage notifications about this

[Bug 1167028] Re: kdeinit4 segmentation fault

2013-04-09 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people

[Bug 1167028] Re: kdeinit4 segmentation fault

2013-04-09 Thread Logan Rosen
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at