LibreOffice Could not attach to process No Stack
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libreoffice (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
System: Linux 2.6.38-
X Vendor: The X.Org Foundation
X Vendor Release: 11001000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Ambiance
Icon Theme: ubuntu-mono-dark
GTK+ Modules: gnomesegvhandler, canberra-gtk-module
Memory status: size: 357085184 vsize: 357085184 resident: 46317568 share: 24903680 rss: 46317568 rss_rlim: 184467440737095
CPU usage: start_time: 1313346517 rtime: 7860 utime: 6942 stime: 918 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100
----------- .xsession-errors -------
** (gnome-
** (gnome-
** (gnome-
** (gnome-
** (gnome-
** (gnome-
** (gnome-
** (gnome-
** (gnome-
Could not attach to process. If your uid matches the uid of the target
process, check the setting of /proc/sys/
again as the root user. For more details, see /etc/sysctl.
ptrace: Операция не позволяется.
/home/fadec/2823: Нет такого файла или каталога.
No stack.
-------
---
Architecture: i386
DistroRelease: Ubuntu 11.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
NonfreeKernelMo
Package: libreoffice 1:3.3.3-1ubuntu2
PackageArchitec
ProcEnviron:
LANGUAGE=ru_RU:en
LANG=ru_RU.UTF-8
SHELL=/bin/bash
ProcVersionSign
Tags: natty
Uname: Linux 2.6.38-
UpgradeStatus: Upgraded to natty on 2011-07-15 (35 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm libvirtd lpadmin netdev plugdev sambashare tape video
Changed in libreoffice (Ubuntu): | |
status: | Incomplete → New |
Changed in libreoffice (Ubuntu): | |
status: | New → Invalid |
Fadec Mirror, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: /wiki.ubuntu. com/ReportingBu gs.
apport-collect 827025
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/