Summary: | Plasma crashes every time... | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Jannis Liapis <ahepas1999> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | ahepas1999, asraniel, barthel.daniel, foss, ljones3, virnik, zokl |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Jannis Liapis
2011-11-15 16:53:38 UTC
I have the similar problem but after upgrade nvidia drivers from 285.03 to 285.05.09 and higher. This problem with libnvidia-tls.so occurs after each start of kde. *** Bug 286851 has been marked as a duplicate of this bug. *** From what i can see, this bug should be reported at nvidia and not here, since the crash is in the nvidia binary driver. bug either in the python bindings or, most likely, in the nvidia blob. not our issue to handle, as Beat notes. *** Bug 287217 has been marked as a duplicate of this bug. *** *** Bug 287937 has been marked as a duplicate of this bug. *** And since I am very sure that the kde developers have a much better communication channel to the nvidia developers than ordinary users it would absolutely make sense that the kde developers would simply forward this issue to the nvidia developers so that this bug the kdedevelopers are blamed for can be solved by the nvidia developers who this way would make the kde developers feel happy to have such a good communication with the nvidia developers. *** Bug 291280 has been marked as a duplicate of this bug. *** For the records: I tried hard to report this issue to NVidia but failed. Although I did not really feel happy about having to create an account at NVidia and all I went through it all since this is a really important issue and the KDE reputation suffers from this kind of stuff. I got three replies from different sections at NVidia, all claiming that they are not responsible for non MS-Windows issues. What is left is: KDE plasma crashes for me and others. Created attachment 67841 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
- What I was doing when the application crashed:
Nothing special, as usual! Plasma crashes every time I open my pc, laptop and desktop but mostly on desktop. This is very very disturbing...
-- Backtrace (Reduced):
#7 0x0844fe80 in _nv019tls () from /usr/lib/nvidia-current/tls/libnvidia-tls.so.290.10
[...]
#9 0x0050bad6 in ptmalloc_unlock_all2 () at arena.c:332
#10 0x00539773 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/i386/../fork.c:170
#11 0x056d8be1 in pipe_open (pstr=2932660260, pname=0xaa2dd90 "nvidia-settings -q [gpu:0]/GPUCoreTemp", mode=0x572e73b "r") at io.c:3255
#12 0x056d91ec in rb_f_backquote (obj=2932227880, str=2932660260) at io.c:4839
Created attachment 67843 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.7.4 (4.7.4) using Qt 4.7.4
- What I was doing when the application crashed:
WTF same shit again...crash reports are popping up like fireworks! FIX IT!!!
-- Backtrace (Reduced):
#7 0x0844fe80 in _nv019tls () from /usr/lib/nvidia-current/tls/libnvidia-tls.so.290.10
[...]
#9 0x0050bad6 in ptmalloc_unlock_all2 () at arena.c:332
#10 0x00539773 in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/i386/../fork.c:170
#11 0x056d8be1 in pipe_open (pstr=2932655000, pname=0xaa2dfe0 "nvidia-settings -q [thermalsensor:0]/ThermalSensorReading", mode=0x572e73b "r") at io.c:3255
#12 0x056d91ec in rb_f_backquote (obj=2932227880, str=2932655000) at io.c:4839
Sorry, Jannis, but this entry has long before been closed as "resolved". Not because it has actually been resolved, but because someone pushed responsibility to NVidia, who in turn denies responsibility. Therefore normal users are left with a crashing desktop. Great, isn't it ? *** Bug 292015 has been marked as a duplicate of this bug. *** *** Bug 294989 has been marked as a duplicate of this bug. *** *** Bug 295144 has been marked as a duplicate of this bug. *** |