| Summary: | Switching back from vtty1 to KDE session results in crash. | ||
|---|---|---|---|
| Product: | [Unmaintained] solid | Reporter: | rtdvrs |
| Component: | general | Assignee: | Alex Fiestas <afiestas> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | adaptee, amantia |
| Priority: | NOR | ||
| Version: | 4.8.4 | ||
| Target Milestone: | 4.11 | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | http://commits.kde.org/kdelibs/c9495ee712035937ed874d76217a7e4f1fc2b3c6 | Version Fixed In: | 4.11 |
| Sentry Crash Report: | |||
|
Description
rtdvrs
2012-06-20 15:47:37 UTC
Well, you certainly did something in TTY1 that caused this, like changing to a static IP or some such? This looks very much like a duplicate of bug 298008 I did no such thing. If you cannot debug it like this add more debugging info. Hi, Can you still reproduce this issue? if so, can you provide the following info? 1-solid-hardware list 2-solid-hardware listen 3-switch to tty and make things crash 4-attach all the outputs :p Thanks ! *** Bug 251356 has been marked as a duplicate of this bug. *** Git commit 75050f6a4dcde0949bbd38d73b6bee44f4d65784 by Àlex Fiestas. Committed on 30/07/2013 at 21:44. Pushed by afiestas into branch 'master'. Always return an object if the device was of interest when added Finally this nasty gets fixed, problem is easy: -Udev calls deviceAdded -We emit deviceAdded -Device becomes invalid (in udev) -UdevManager::createDevice is called, returns 0 -deviceRemoved is emit -Q_ASSERT explodes because we returned 0. This patch basically ensures that if the device was of interest when deviceAdded was called a UdevDevice object is always returned even if the device is dummy. That's the best we can do. FIXED-IN: 4.11 M +27 -6 solid/solid/backends/udev/udevmanager.cpp http://commits.kde.org/kdelibs/75050f6a4dcde0949bbd38d73b6bee44f4d65784 Git commit c9495ee712035937ed874d76217a7e4f1fc2b3c6 by Àlex Fiestas. Committed on 30/07/2013 at 21:44. Pushed by afiestas into branch 'KDE/4.11'. Always return an object if the device was of interest when added Finally this nasty gets fixed, problem is easy: -Udev calls deviceAdded -We emit deviceAdded -Device becomes invalid (in udev) -UdevManager::createDevice is called, returns 0 -deviceRemoved is emit -Q_ASSERT explodes because we returned 0. This patch basically ensures that if the device was of interest when deviceAdded was called a UdevDevice object is always returned even if the device is dummy. That's the best we can do. FIXED-IN: 4.11 (cherry picked from commit 75050f6a4dcde0949bbd38d73b6bee44f4d65784) M +27 -6 solid/solid/backends/udev/udevmanager.cpp http://commits.kde.org/kdelibs/c9495ee712035937ed874d76217a7e4f1fc2b3c6 |