[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Apologies for my previous message. Somehow I missed that a proposed fix was available for testing. I'm having trouble figuring out how to download the proposed fix, but I'm sure I can figure it out with time and research. It's been years since any variant of Linux has been my primary personal OS, so I'm still in the early stages of re- familiarizing myself with everything. By the way, since I forgot to include it before: uname -a Linux Ubuntu-Desktop 4.18.0-16-generic #17~18.04.1-Ubuntu SMP Tue Feb 12 13:35:51 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux gnome-shell --version GNOME Shell 3.28.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Is there any fix or workaround for this bug? I installed a brand new copy of Ubuntu 18.04 on a brand new 512 GB SSD three days ago on Saturday evening (2019-03-09). I installed online updates during installation. It is now Tuesday evening (2019-03-12). The computer has been locked for most of the time since installation. In my /var/log directory, I have two enormous files: syslog (188.2 GB) syslog.1 (264.5 GB) And one smaller compressed older file: syslog.2.gz (313.6 MB) (I can confirm the issue I am experiencing is the error related to "osdWindow.js:207" on 18.04.) This needs a fix ASAP! I can't have my desktop filling up its storage with hundreds of gigs of errors every day! (~188 + ~264= ~452 GB in two or three days) I've attached the output of ls -l /var/log for proof since these are some of the largest hard numbers I've seen mentioned in this thread. ** Attachment added: "Output of: ls -l /var/log" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+attachment/5245730/+files/filesizes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2
[Desktop-packages] [Bug 1380028] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Public bug reported: Failed to build on update to Kernel 3.16.0.22 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 DKMSKernelVersion: 3.16.0-22-generic Date: Sat Oct 11 10:17:57 2014 InstallationDate: Installed on 2014-07-11 (91 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140709) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1380028 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Failed to build on update to Kernel 3.16.0.22 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4 Uname: Linux 3.16.0-22-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 DKMSKernelVersion: 3.16.0-22-generic Date: Sat Oct 11 10:17:57 2014 InstallationDate: Installed on 2014-07-11 (91 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140709) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1380028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1378906] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
Public bug reported: Failed to build on update to 3.16.0.21 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 DKMSKernelVersion: 3.16.0-21-generic Date: Wed Oct 8 11:31:48 2014 InstallationDate: Installed on 2014-07-11 (88 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140709) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1378906 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Failed to build on update to 3.16.0.21 ProblemType: Package DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu5 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 DKMSKernelVersion: 3.16.0-21-generic Date: Wed Oct 8 11:31:48 2014 InstallationDate: Installed on 2014-07-11 (88 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140709) PackageVersion: 331.89-0ubuntu5 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1378906/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 935741] Re: soffice.bin crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
*** This bug is a duplicate of bug 919020 *** https://bugs.launchpad.net/bugs/919020 This particular crash has already been reported and is a duplicate of bug #919020, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. BUT bug #919020 cannot be found! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/935741 Title: soffice.bin crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in “libreoffice” package in Ubuntu: New Bug description: Libre Office crashed while I was cutting a pasting from a website ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.5.0~beta2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Sat Feb 18 21:37:39 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2007) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer /home/username/Documents/Raymond\ Blanc\ receipes.odt --splash-pipe=6 Signal: 6 SourcePackage: libreoffice StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 cppu::loadSharedLibComponentFactory(rtl::OUString const, rtl::OUString const, rtl::OUString const, com::sun::star::uno::Referencecom::sun::star::lang::XMultiServiceFactory const, com::sun::star::uno::Referencecom::sun::star::registry::XRegistryKey const, rtl::OUString const) () from /usr/lib/libreoffice/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3 Title: soffice.bin crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to precise on 2012-02-17 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/935741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915673] Re: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915673 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 Status in “libreoffice” package in Ubuntu: New Bug description: During partial distribution update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 23:33:11 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2007) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915673] [NEW] package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
Public bug reported: During partial distribution update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 23:33:11 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2007) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915673 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 Status in “libreoffice” package in Ubuntu: New Bug description: During partial distribution update ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0 Uname: Linux 3.2.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 23:33:11 2012 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (2007) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915673/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915271] Re: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty
worked for me thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/915271 Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty Status in LibreOffice Productivity Suite: New Status in “libreoffice” package in Ubuntu: Confirmed Bug description: running updates/upgrades on Precise machine and message popped up saying it needed to report this bug. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libreoffice-core 1:3.4.4-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic x86_64 ApportVersion: 1.90-0ubuntu1 Architecture: amd64 Date: Thu Jan 12 11:44:43 2012 DuplicateSignature: Unpacking replacement libreoffice-math ... Preparing to replace libreoffice-core 1:3.4.4-0ubuntu2 (using .../libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb) ... rmdir: failed to remove `usr/lib/libreoffice/basis3.4/program/': Directory not empty dpkg: error processing /var/cache/apt/archives/libreoffice-core_1%3a3.5.0~beta2-2ubuntu2_amd64.deb (--unpack): subprocess new pre-installation script returned error exit status 1 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: libreoffice Title: package libreoffice-core 1:3.4.4-0ubuntu2 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: Upgraded to precise on 2012-01-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915271/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 833087] Re: gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke()
Input 'apt-get update apt-get upgrade' into Terminal. After reboot, I received the error. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/833087 Title: gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke() Status in “gnome-settings-daemon” package in Ubuntu: Won't Fix Bug description: occured today after update, immediately after login. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.1.5-0ubuntu5 ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 Date: Wed Aug 24 10:29:55 2011 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /home/robbiew ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f63379807b0:mov0x8(%rax),%rcx PC (0x7f63379807b0) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rcx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-settings-daemon crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/833087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
