Fix committed upstream for KDE 4.4.4. Will make an SRU for Lucid.

** Also affects: kdebase-runtime (Ubuntu Lucid)
   Importance: Undecided
       Status: New

** Changed in: kdebase-runtime (Ubuntu Lucid)
   Importance: Undecided => Medium

** Changed in: kdebase-runtime (Ubuntu Lucid)
     Assignee: (unassigned) => Jonathan Thomas (echidnaman)

** Changed in: kdebase-runtime (Ubuntu)
     Assignee: (unassigned) => Jonathan Thomas (echidnaman)

** Description changed:

  ##SRU information added by Jonathan Thomas##
  Impact: Causes the nepomukstorage nepomukservicestub to often crash on login
- The problem: Upstream had forgotten to initialize some member variables in 
the Nepomuk::Repository::Repository constructor. Due to this, if anything 
requested the use of the nepomuk storage service before the soprano backend was 
ready, a crash due to accessing uninitialized variables resulted.
- Addressed by: Upstream committed a patch to the stable 4.4 branch that 
initializes the offending member variables.
+ 
+ The problem: Upstream had forgotten to initialize some member variables
+ in the Nepomuk::Repository::Repository constructor. Due to this, if
+ anything requested the use of the nepomuk storage service before the
+ soprano backend was ready, a crash due to accessing uninitialized
+ variables resulted.
+ 
+ Addressed by: Upstream committed a patch to the stable 4.4 branch that
+ initializes the offending member variables.
+ 
  Patch: http://websvn.kde.org/?revision=1123884&view=revision
- Testcase: None available. It was much easier to see when apport was on, as 
this is a background service, but we were never able to get anything solid on 
how to reproduce.
+ 
+ Testcase: None available. It was much easier to see when apport was on,
+ as this is a background service, but we were never able to get anything
+ solid on how to reproduce.
+ 
  Regression potential: Zero. It never hurts to initialize variables in the 
class constructor, especially when you know that they may be accessed before 
they are initialized elsewhere in the code.
  ###############################
  
  Binary package hint: kdebase-runtime
  
  I just try toi enable Nepomuki and after few second get crash.
  
  ProblemType: Crash
  Architecture: amd64
  Date: Sat Feb  6 16:59:26 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/nepomukservicestub
  InstallationMedia: Error: [Errno 13] Отказано в доступе: 
'/var/log/installer/media-info'
  NonfreeKernelModules: nvidia
  Package: kdebase-runtime 4:4.3.98-0ubuntu1
  ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
   LANGUAGE=
  ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
  SegvAnalysis:
   Segfault happened at: 0x7f0b2216e434 <_ZNK7Soprano6Plugin10pluginNameEv+4>:  
mov    0x8(%rsi),%rcx
   PC (0x7f0b2216e434) ok
   source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: kdebase-runtime
  StacktraceTop:
   Soprano::Plugin::pluginName() const ()
   ?? () from /usr/lib/kde4/nepomukstorage.so
   ?? () from /usr/lib/kde4/nepomukstorage.so
   ?? () from /usr/lib/kde4/nepomukstorage.so
   ?? () from /usr/lib/libQtDBus.so.4
  Title: nepomukservicestub crashed with SIGSEGV in 
Soprano::Plugin::pluginName()
  Uname: Linux 2.6.32-12-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (process:2221): GLib-CRITICAL **: g_once_init_leave: assertion 
`initialization_value != 0' failed
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead

** Description changed:

  ##SRU information added by Jonathan Thomas##
- Impact: Causes the nepomukstorage nepomukservicestub to often crash on login
+ Impact: Causes the nepomukstorage nepomukservicestub to often crash on login. 
It affects 12 people, which is kind of a lot for a Kubuntu bug. (Multiply 
affected users by 4 to get what it would be like for a bug affecting Ubuntu)
  
  The problem: Upstream had forgotten to initialize some member variables
  in the Nepomuk::Repository::Repository constructor. Due to this, if
  anything requested the use of the nepomuk storage service before the
  soprano backend was ready, a crash due to accessing uninitialized
  variables resulted.
  
  Addressed by: Upstream committed a patch to the stable 4.4 branch that
  initializes the offending member variables.
  
  Patch: http://websvn.kde.org/?revision=1123884&view=revision
  
  Testcase: None available. It was much easier to see when apport was on,
  as this is a background service, but we were never able to get anything
  solid on how to reproduce.
  
  Regression potential: Zero. It never hurts to initialize variables in the 
class constructor, especially when you know that they may be accessed before 
they are initialized elsewhere in the code.
  ###############################
  
  Binary package hint: kdebase-runtime
  
  I just try toi enable Nepomuki and after few second get crash.
  
  ProblemType: Crash
  Architecture: amd64
  Date: Sat Feb  6 16:59:26 2010
  DistroRelease: Ubuntu 10.04
  ExecutablePath: /usr/bin/nepomukservicestub
  InstallationMedia: Error: [Errno 13] Отказано в доступе: 
'/var/log/installer/media-info'
  NonfreeKernelModules: nvidia
  Package: kdebase-runtime 4:4.3.98-0ubuntu1
  ProcCmdline: /usr/bin/nepomukservicestub nepomukstorage
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
   LANGUAGE=
  ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
  SegvAnalysis:
   Segfault happened at: 0x7f0b2216e434 <_ZNK7Soprano6Plugin10pluginNameEv+4>:  
mov    0x8(%rsi),%rcx
   PC (0x7f0b2216e434) ok
   source "0x8(%rsi)" (0x00000008) not located in a known VMA region (needed 
readable region)!
   destination "%rcx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: kdebase-runtime
  StacktraceTop:
   Soprano::Plugin::pluginName() const ()
   ?? () from /usr/lib/kde4/nepomukstorage.so
   ?? () from /usr/lib/kde4/nepomukstorage.so
   ?? () from /usr/lib/kde4/nepomukstorage.so
   ?? () from /usr/lib/libQtDBus.so.4
  Title: nepomukservicestub crashed with SIGSEGV in 
Soprano::Plugin::pluginName()
  Uname: Linux 2.6.32-12-generic x86_64
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  XsessionErrors:
   (process:2221): GLib-CRITICAL **: g_once_init_leave: assertion 
`initialization_value != 0' failed
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead
   (exe:9200): Gdk-WARNING **: XID collision, trouble ahead

-- 
nepomukservicestub crashed with SIGSEGV in Soprano::Plugin::pluginName()
https://bugs.launchpad.net/bugs/517962
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdebase-runtime in ubuntu.

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

Reply via email to