[Bug 1937924] Re: kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry Pi4B
> Are you still having issues when running 22.04 jammy? Sorry, I'm no longer running Ubuntu on the device. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937924 Title: kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry Pi4B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1937924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967698] [NEW] Just displays a blank window when running on Wayland
Public bug reported: $ lsb_release -rd Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 $ apt-cache policy stellarium stellarium: Installed: 0.20.4-3 Candidate: 0.20.4-3 Version table: *** 0.20.4-3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status When using Wayland, I expect the application to display a window with controls and sky display. Instead a blank window with a black background is displayed. There are no controls or sky displayed. Running under x-org works as expected. Graphics: OpenGL version string: 4.6.0 NVIDIA 510.60.02 Running from a terminal gives this text: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. - [ This is Stellarium 0.20.4 - https://stellarium.org/ ] [ Copyright (C) 2000-2021 Fabien Chereau et al. ] - Writing log file to: "/home/paul/.stellarium/log.txt" File search paths: 0 . "/home/paul/.stellarium" 1 . "/usr/share/stellarium" Config file is: "/home/paul/.stellarium/config.ini" Default surface format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Desired surface format: QSurfaceFormat(version 2.1, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) StelGLWidget constructor StelGraphicsScene constructor QOpenGLWidget: Failed to make context current QPainter::begin: Paint device returned engine == 0, type: 1 QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::setRenderHint: Painter must be active to set rendering hints QPainter::worldTransform: Painter not active QPainter::save: Painter not active QPainter::restore: Unbalanced save/restore QPainter::setWorldTransform: Painter not active QPainter::end: Painter not active, aborted Running with QT_QPA_PLATFORM=wayland stellarium core dumps with (non of the suggestions work): Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.plugin: Could not find the Qt platform plugin "wayland" in "" This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. Aborted (core dumped) ** Affects: stellarium (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Just displays a blank window + Just displays a blank window using Wayland ** Summary changed: - Just displays a blank window using Wayland + Just displays a blank window when running on Wayland ** Description changed: $ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 - $ apt-cache policy stellarium stellarium: - Installed: 0.20.4-3 - Candidate: 0.20.4-3 - Version table: - *** 0.20.4-3 500 - 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 0.20.4-3 + Candidate: 0.20.4-3 + Version table: + *** 0.20.4-3 500 + 500 http://gb.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages + 100 /var/lib/dpkg/status I expect the application to display window with controls and sky display. Instead a blank, window with a black background is displayed. There are no controls or sky displayed. + Graphics: + OpenGL version string: 4.6.0 NVIDIA 510.60.02 + + Running from a terminal gives this text: Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. - - + - [ This is Stellarium 0.20.4 - https://stellarium.org/ ] [ Copyright (C) 2000-2021 Fabien Chereau et al. ] - - + - Writing log file to: "/home/paul/.stellarium/log.txt" File search paths: - 0 . "/home/paul/.stellarium" - 1 . "/usr/share/stellarium" + 0 . "/home/paul/.stellarium" + 1 . "/usr/share/stellarium" Config file is: "/home/paul/.stellarium/config.ini" Default surface format: QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize -1, greenBufferSize -1, b
[Bug 1935767] Re: vanilla-gnome-default-settings will not install for impish-proposed
Thanks for the fix, I can confirm the update for Jammy installed without errors and "apt purge" and "apt install" on the package worked too. Will you be back porting the fix to impish? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935767 Title: vanilla-gnome-default-settings will not install for impish-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1935767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935767] Re: vanilla-gnome-default-settings will not install for impish-proposed
Patch attached ** Attachment added: "ubuntu-gnome-default-settings-patch-bug-1935767" https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1935767/+attachment/5525486/+files/ubuntu-gnome-default-settings-patch-bug-1935767 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935767 Title: vanilla-gnome-default-settings will not install for impish-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1935767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935767] Re: vanilla-gnome-default-settings will not install for impish-proposed
I have a manual fix for this. Edit "/var/lib/dpkg/info/vanilla-gnome-default-settings.postinst" Change "gdm3-theme.gresource" to "gdm-theme.gresource" Then "sudo apt install -f" The vanilla gnome setup now works as expected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935767 Title: vanilla-gnome-default-settings will not install for impish-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1935767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943097] Re: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb
I'm also experiencing this after the latest 21.10 update on two builds on the same Raspberry Pi 400, booting from USB. I added a comment on https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1937924 which sounded similar. I have restored a bootable system by mounting the devices on another machine and replacing initrd.img and vmlinuz on the boot partition with the .bak versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943097 Title: Kernel 5.13 broke my Ubuntu 21.10 on RPI4 8Gb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943097/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937924] Re: kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry Pi4B
I think I have the same issue but I'm not sure. I have a Rasp IP 400 that I've been running Ubuntu 21.10 desktop (vanilla Gnome via the vanilla packages) on for about a month. I'm booting directly from a USB attached disk. This weekend I did updates as I do most days but this time the system will no longer boot. I'm not familiar with the boot process on Arm/PIs so have been unable to fix it. I needed the machine so I used a fresh install on a different disk and keeping to 21.04. Today, missing Gnome 40, I decided to upgrade using "do-release-upgrade -d". All looked fine until the restart, the machine fails to boot. I'll try recovering the installs using the suggested method but it could be an issue with the latest kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937924 Title: kernel upgrade via apt 5.11.0.1015-raspi kills the OS on Raspberry Pi4B To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1937924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935767] [NEW] vanilla-gnome-default-settings will not install for impish-proposed
Public bug reported: Keen to try out Gnome 40 on impish, I enabled impish-proposed and updated, all was fine. I prefer the upstream vanilla gnome experience so installed vanilla-gnome-desktop which depends on vanilla-gnome- default-settings. However, vanilla-gnome-default-settings installation failed: Setting up vanilla-gnome-default-settings (20.04.1) ... update-alternatives: error: no alternatives for gdm3-theme.gresource dpkg: error processing package vanilla-gnome-default-settings (--configure): installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: vanilla-gnome-default-settings E: Sub-process /usr/bin/dpkg returned an error code (1) 1) $ lsb_release -rd Description:Ubuntu Impish Indri (development branch) Release:21.10 2) $ apt-cache policy vanilla-gnome-default-settings vanilla-gnome-default-settings: Installed: 20.04.1 Candidate: 20.04.1 Version table: *** 20.04.1 500 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages 100 /var/lib/dpkg/status 3) I would expect the package to install without errors. 4) Instead it does not complete installation. Further attempts to --configure etc also fail. I understand this is software in development, I'm just trying to help. Thanks for all your hard work. ** Affects: ubuntu-gnome-default-settings (Ubuntu) Importance: Undecided Status: New ** Description changed: Keen to try out Gnome 40 on impish, I enabled impish-proposed and updated, all was fine. I prefer the upstream vanilla gnome experience so installed vanilla-gnome-desktop which depends on vanilla-gnome- default-settings. However, vanilla-gnome-default-settings installation failed: Setting up vanilla-gnome-default-settings (20.04.1) ... update-alternatives: error: no alternatives for gdm3-theme.gresource dpkg: error processing package vanilla-gnome-default-settings (--configure): - installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 + installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 Errors were encountered while processing: - vanilla-gnome-default-settings + vanilla-gnome-default-settings E: Sub-process /usr/bin/dpkg returned an error code (1) 1) $ lsb_release -rd Description: Ubuntu Impish Indri (development branch) Release: 21.10 2) $ apt-cache policy vanilla-gnome-default-settings vanilla-gnome-default-settings: - Installed: 20.04.1 - Candidate: 20.04.1 - Version table: - *** 20.04.1 500 - 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages - 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages - 100 /var/lib/dpkg/status + Installed: 20.04.1 + Candidate: 20.04.1 + Version table: + *** 20.04.1 500 + 500 http://gb.archive.ubuntu.com/ubuntu impish/universe amd64 Packages + 500 http://gb.archive.ubuntu.com/ubuntu impish/universe i386 Packages + 100 /var/lib/dpkg/status 3) I would expect the package to install without errors. 4) Instead it does not complete installation. + Further attempts to --configure etc also fail. + I understand this is software in development, I'm just trying to help. Thanks for all your hard work. ** Summary changed: - vanilla-gnome-default-settings will not install + vanilla-gnome-default-settings will not install for impish-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935767 Title: vanilla-gnome-default-settings will not install for impish-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1935767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.
Confirmed also, now starts as normal. Thanks for the fix. $ apt-cache policy nextcloud-desktop nextcloud-desktop: Installed: 3.1.1-1ubuntu1.1 Candidate: 3.1.1-1ubuntu1.1 Version table: *** 3.1.1-1ubuntu1.1 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 3.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu hirsute/universe amd64 Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: [SRU] nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: nextcloud crashed with SIGSEGV.
I do not get the crash on arm, this is a raspberry pi 400 machine. $ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 $ apt-cache policy nextcloud-desktop nextcloud-desktop: Installed: 3.1.1-1ubuntu1 Candidate: 3.1.1-1ubuntu1 Version table: *** 3.1.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute/universe arm64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923053] Re: nextcloud crashed with SIGSEGV.
** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+attachment/5485597/+files/CoreDump.gz ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923053 Title: nextcloud crashed with SIGSEGV. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 253119] Re: PPA packages do not show a changelog in update-manager
Yes, this was implemented a while ago, sorry if I should have closed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/253119 Title: PPA packages do not show a changelog in update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/253119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870795] Re: Appindicator not showing under wayland
On a fully up to date install of Ubuntu focal, I confirmed that the bug still existing using the current version gnome-shell-extension- appindicator/33.1. I then installed and tested the new version gnome- shell-extension-appindicator/33.1-0ubuntu0.20.04.1 and can confirm the bug no longer occurs with the steps outlined in the top description. Thanks for the fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870795] Re: Appindicator not showing under wayland
Put back to new as I've added the requested information. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872857] [NEW] attribute-invalid : timestamp is in the future
Public bug reported: $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy libappstream-glib8 libappstream-glib8: Installed: 0.7.16-1ubuntu1 Candidate: 0.7.16-1ubuntu1 Version table: *** 0.7.16-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I'm UK based with time set to BST. If I set the date to the current date, then between 12:00 midnight and 1:00am, flatpak-builder fails with and error: org.pjbroad.EternallandsClient:AppData problem: attribute-invalid : timestamp is in the future Error loading AppData file: AppData file /app/share/appdata/org.pjbroad.EternallandsClient.appdata.xml was not valid Error: ERROR: appstream-compose failed: Child process exited with code 1 I would expect using my local date to be valid. This bug is fixed upstream in version 0.7.17 https://github.com/hughsie/appstream-glib/commit/72789b6ff59f5d1741d1cbc29e90bfa57079c514 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libappstream-glib8 0.7.16-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Apr 15 00:31:43 2020 InstallationDate: Installed on 2019-11-02 (164 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: appstream-glib UpgradeStatus: Upgraded to focal on 2020-03-28 (17 days ago) ** Affects: appstream-glib (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872857 Title: attribute-invalid : timestamp is in the future To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1872857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870795] Re: Appindicator not showing under wayland
The journalctl output is very verbose and contains all my system information, do you really want and need all that or is there a particular section? Below is a portion that mentions app indicator. If I lock my screen, then unlock, the output includes a few additional lines but nothing about app-indicator. My only indicator is one I wrote myself: https://launchpad.net/el-time-applet/appindicator If there is another indicator you want me to test to rule out an error my part then please let me know. Thanks, Paul Apr 07 20:06:22 padfoot colord[1774]: failed to get session [pid 20630]: No data available Apr 07 20:06:22 padfoot gnome-shell[20125]: Failed to set CRTC gamma: drmModeCrtcSetGamma on CRTC 48 failed: Permission denied Apr 07 20:06:22 padfoot gnome-shell[20478]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed Apr 07 20:06:22 padfoot gnome-shell[20478]: JS ERROR: TypeError: src is null connectSmart4A@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:189:21 connectSmart@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/util.js:214:31 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/appIndicator.js:325:14 _init@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/indicatorStatusIcon.js:42:25 _registerItem@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:95:22 _ensureItemRegistered@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:123:14 RegisterStatusNotifierItemAsync@/usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com/statusNotifierWatcher.js:169:14 _handleMethodCall@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:371:35 _wrapJSObject/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:404:34 Apr 07 20:06:22 padfoot systemd[20398]: GNOME session X11 services is not active. Apr 07 20:06:22 padfoot systemd[20398]: Dependency failed for GNOME XSettings. Apr 07 20:06:22 padfoot systemd[20398]: gsd-xsettings.target: Job gsd-xsettings.target/start failed with result 'dependency'. Apr 07 20:06:22 padfoot gnome-shell[20478]: GNOME Shell started at Tue Apr 07 2020 20:06:20 GMT+0100 (BST) Apr 07 20:06:22 padfoot gnome-shell[20478]: Registering session with GDM Apr 07 20:06:22 padfoot systemd[20398]: Starting GNOME XSettings... Apr 07 20:06:22 padfoot systemd[20031]: Stopped target GNOME Wayland Session (session: gnome-login). Apr 07 20:06:22 padfoot systemd[20031]: Stopped target Current graphical user session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870795] Re: Appindicator not showing under wayland
That formatting is bad, here and attachment. ** Attachment added: "journalctl-output.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+attachment/5348988/+files/journalctl-output.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1870795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868914] Re: package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit sta
Late I know, but I can confirm the PPA versions fix the package issues. Thanks for your work Tim. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868914 Title: package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1868914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870795] [NEW] Appindicator not showing under wayland
Public bug reported: $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache policy gnome-session-wayland gnome-session-wayland: Installed: (none) Candidate: 3.36.0-2ubuntu1 Version table: 3.36.0-2ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu focal/universe i386 Packages An app-indicator icon does not show when I login using the default gnome session (wayland). If I choose the xorg session, the icon shows as normal. Under wayland, the icon does appear if I lock my session then log back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-session-wayland (not installed) ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Apr 4 15:30:40 2020 InstallationDate: Installed on 2019-12-15 (111 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-session UpgradeStatus: Upgraded to focal on 2020-03-10 (24 days ago) ** Affects: gnome-session (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870795 Title: Appindicator not showing under wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1870795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868914] Re: package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit sta
This issue also caused an update to 20.04 to fail for a system that had vanilla-gnome-default-settings already installed. I had to manually edit the install scripts for vanilla-gnome-default-settings to enable the update to complete. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868914 Title: package vanilla-gnome-default-settings 18.10.1 failed to install/upgrade: installed vanilla-gnome-default-settings package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-default-settings/+bug/1868914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846083] [NEW] App Icons disappear on cursor hover
Public bug reported: Click show applications then mouse over the icons. They disappear when they should not. This has been reported and fixed upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1502 $ lsb_release -rd Description:Ubuntu Eoan Ermine (development branch) Release:19.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.34.0-1ubuntu1 Candidate: 3.34.0-1ubuntu1 Version table: *** 3.34.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: gnome-shell (Fedora) Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1753337 https://bugzilla.redhat.com/show_bug.cgi?id=1753337 ** Also affects: gnome-shell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1753337 Importance: Unknown Status: Unknown ** Description changed: Click show applications then mouse over the icons. They disappear when they should not. This has been reported and fixed upstream. + + https://gitlab.gnome.org/GNOME/gnome-shell/issues/1502 $ lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 $ apt-cache policy gnome-shell gnome-shell: - Installed: 3.34.0-1ubuntu1 - Candidate: 3.34.0-1ubuntu1 - Version table: - *** 3.34.0-1ubuntu1 500 - 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.34.0-1ubuntu1 + Candidate: 3.34.0-1ubuntu1 + Version table: + *** 3.34.0-1ubuntu1 500 + 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages + 100 /var/lib/dpkg/status ** Description changed: Click show applications then mouse over the icons. They disappear when - they should not. This has been reported and fixed upstream. + they should not. + This has been reported and fixed upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1502 $ lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.34.0-1ubuntu1 Candidate: 3.34.0-1ubuntu1 Version table: *** 3.34.0-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846083 Title: App Icons disappear on cursor hover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1846083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825903] Re: import PythonMagick fails with undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv
I tried python-pythonmagick_0.9.19-4_amd64.deb from eoan which works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825903 Title: import PythonMagick fails with undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pythonmagick/+bug/1825903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825903] Re: import PythonMagick fails with undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv
Is there a way to find out if the Debian fix is going to be pulled into disco? This bug also effects the python3 package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825903 Title: import PythonMagick fails with undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pythonmagick/+bug/1825903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825903] [NEW] import PythonMagick fails with undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv
Public bug reported: $ python Python 2.7.16 (default, Apr 6 2019, 01:42:57) [GCC 8.3.0] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import PythonMagick Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/PythonMagick/__init__.py", line 1, in from . import _PythonMagick ImportError: /usr/lib/python2.7/dist-packages/PythonMagick/_PythonMagick.x86_64-linux-gnu.so: undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv $ lsb_release -rd Description:Ubuntu 19.04 Release:19.04 $ apt-cache policy python-pythonmagick python-pythonmagick: Installed: 0.9.19-2 Candidate: 0.9.19-2 Version table: *** 0.9.19-2 500 500 http://gb.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status Module should import without errors, instead module fails with error "undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv" ** Affects: pythonmagick (Ubuntu) Importance: Undecided Status: New ** Tags: disco ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825903 Title: import PythonMagick fails with undefined symbol: _Z41Export_pyste_src_DrawableStrokeDashOffsetv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pythonmagick/+bug/1825903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822220] Re: package libnvidia-compute-410 (not installed) failed to install/upgrade: package libnvidia-compute-410:i386 (418.56-0ubuntu1) with field 'Multi-Arch: no' is not co-installable with l
This happened to me during a "do-release-update -d" on my 19.04 system. I found a reference to a similar issue here: https://askubuntu.com/questions/146150/unable-to-fix-broken-packages- with-sudo-apt-get-install-f I made a copy of /var/lib/dpkg/status then edited it to remove all the sections about the package libnvidia-compute-410. I then did "sudo apt --fix-broken install" which completed successfully. I have continued the update manually using "sudo apt-get update && sudo apt-get upgrade && sudo apt-get dist-upgrade". I would appreciate know if this was the correct thing to do and if I need to do any further repair to properly remove the broken package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/180 Title: package libnvidia-compute-410 (not installed) failed to install/upgrade: package libnvidia-compute-410:i386 (418.56-0ubuntu1) with field 'Multi-Arch: no' is not co-installable with libnvidia- compute-410 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822220] Re: package libnvidia-compute-410 (not installed) failed to install/upgrade: package libnvidia-compute-410:i386 (418.56-0ubuntu1) with field 'Multi-Arch: no' is not co-installable with l
Correction, this was a "do-release-update -d" on my 18.10 system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/180 Title: package libnvidia-compute-410 (not installed) failed to install/upgrade: package libnvidia-compute-410:i386 (418.56-0ubuntu1) with field 'Multi-Arch: no' is not co-installable with libnvidia- compute-410 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799305] Re: No desktop after reboot when using nvidia graphics on 18.10
Yes, looks like it and editing /etc/gdm3/custom.conf to set "WaylandEnable=false" fixed the issue for me too. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799305 Title: No desktop after reboot when using nvidia graphics on 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799305] Re: No desktop at boot after upgrade form 18.04 to 18.10
** Description changed: - I upgraded from 18.04 to 18.10 and now the desktop does not start on a - fresh boot. The console output ends with "Starting GNOME Display + I upgraded from 18.04 to 18.10 and now the desktop does not start after + a reboot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop - starts as expected from a clean boot. Examining /var/log/syslog appears - to show the nvidia driver failing to load correctly; see below. + starts as expected after reboot. Examining /var/log/syslog appears to + show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.
[Bug 1799305] Re: No desktop at boot after upgrade form 18.04 to 18.10
** Description changed: - I upgrade from 18.04 to 18.10 and now the desktop does not start on a + I upgraded from 18.04 to 18.10 and now the desktop does not start on a fresh boot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop starts as expected from a clean boot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. . . . This is a section from syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description: Ubuntu 18.10 Release: 18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 22 22:32:04 2018 InstallationDate: I
[Bug 1799305] Re: No desktop at boot after upgrade form 18.04 to 18.10
The issue persists after installing nvidia-410 from the “Graphics Drivers” team PPA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799305 Title: No desktop at boot after upgrade form 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1799305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799305] Re: No desktop at boot after upgrade form 18.04 to 18.10
** Description changed: I upgrade from 18.04 to 18.10 and now the desktop does not start on a fresh boot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I - can restart run "systemctrl restart gdm3" and I get a working login - screen and can continue as expected. If I remove my nvidia drivers the - desktop start as expected from a clean boot. Examining /var/log/syslog - appears to show the nvidia driver failing to load correctly; see below. + can run "systemctrl restart gdm3" and I get a working login screen and + can continue as expected. If I remove my nvidia drivers the desktop + starts as expected from a clean boot. Examining /var/log/syslog appears + to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager -Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) -Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago - Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) - Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) - Main PID: 1880 (gdm3) - Tasks: 3 (limit: 4915) -Memory: 5.7M -CGroup: /system.slice/gdm.service -└─1880 /usr/sbin/gdm3 + Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) + Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago + Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) + Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) + Main PID: 1880 (gdm3) + Tasks: 3 (limit: 4915) + Memory: 5.7M + CGroup: /system.slice/gdm.service + └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. This is a section form syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2
[Bug 1799305] [NEW] No desktop at boot after upgrade form 18.04 to 18.10
Public bug reported: I upgrade from 18.04 to 18.10 and now the desktop does not start on a fresh boot. The console output ends with "Starting GNOME Display Manager". I cannot switch VTs, my keyboard and mouse are unresponsive though RESUIB sequence works to reboot. If I remote login using ssh, I can restart run "systemctrl restart gdm3" and I get a working login screen and can continue as expected. If I remove my nvidia drivers the desktop start as expected from a clean boot. Examining /var/log/syslog appears to show the nvidia driver failing to load correctly; see below. In the failed state "systemctl status gdm3" shows: ● gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static; vendor preset: enabled) Active: active (running) since Mon 2018-10-22 22:06:38 BST; 16min ago Process: 1877 ExecStartPre=/usr/lib/gdm3/gdm-wait-for-drm (code=exited, status=0/SUCCESS) Process: 1723 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1880 (gdm3) Tasks: 3 (limit: 4915) Memory: 5.7M CGroup: /system.slice/gdm.service └─1880 /usr/sbin/gdm3 Oct 22 22:06:35 hagrid systemd[1]: Starting GNOME Display Manager... Oct 22 22:06:38 hagrid systemd[1]: Started GNOME Display Manager. Oct 22 22:06:44 hagrid gdm-launch-environment][2108]: pam_unix(gdm-launch-environment:session): session opened for user gdm by (uid=0) Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3[1880]: Child process -2634 was already dead. root@hagrid:/var/log# grep 2634 syslog Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. This is a section form syslog: Oct 22 22:06:53 hagrid systemd[1]: Starting NVIDIA Persistence Daemon... Oct 22 22:06:53 hagrid nvidia-persistenced: Verbose syslog connection opened Oct 22 22:06:53 hagrid systemd[1]: Started NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Now running with user ID 123 and group ID 129 Oct 22 22:06:54 hagrid [2750]: meta_kms_resources_init failed: Calling drmModeGetResources() failed, assuming we have no outputs Oct 22 22:06:54 hagrid gnome-session[2664]: gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid nvidia-persistenced: Started (2865) Oct 22 22:06:54 hagrid [2750]: Failed to create backend: No GPUs with outputs found Oct 22 22:06:54 hagrid nvidia-persistenced: device :01:00.0 - registered Oct 22 22:06:54 hagrid gnome-session-binary[2664]: Unrecoverable failure in required component org.gnome.Shell.desktop Oct 22 22:06:54 hagrid nvidia-persistenced: Local RPC service initialized Oct 22 22:06:54 hagrid systemd[1]: Stopping NVIDIA Persistence Daemon... Oct 22 22:06:54 hagrid kernel: [ 86.847749] virbr0: port 1(virbr0-nic) entered blocking state Oct 22 22:06:54 hagrid kernel: [ 86.847753] virbr0: port 1(virbr0-nic) entered listening state Oct 22 22:06:54 hagrid gnome-session-binary[2664]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1 Oct 22 22:06:54 hagrid systemd[1]: Stopped NVIDIA Persistence Daemon. Oct 22 22:06:54 hagrid nvidia-persistenced: Received signal 15 Oct 22 22:06:54 hagrid nvidia-persistenced: Socket closed. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file unlocked. Oct 22 22:06:54 hagrid systemd[1]: user-runtime-dir@121.service: Unit not needed anymore. Stopping. Oct 22 22:06:54 hagrid nvidia-persistenced: PID file closed. Oct 22 22:06:54 hagrid systemd[1]: Stopping User Manager for UID 121... Oct 22 22:06:54 hagrid nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced Oct 22 22:06:54 hagrid systemd[2507]: Stopping D-Bus User Message Bus... Oct 22 22:06:54 hagrid nvidia-persistenced: Shutdown (2865) Oct 22 22:06:54 hagrid systemd[2507]: Stopped target Default. Oct 22 22:06:54 hagrid systemd[2507]: Stopped D-Bus User Message Bus. Oct 22 22:06:54 hagrid gdm3: Child process -2634 was already dead. Description:Ubuntu 18.10 Release:18.10 nvidia-driver-390: Installed: 390.87-0ubuntu1 Candidate: 390.87-0ubuntu1 Version table: *** 390.87-0ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu cosmic/restricted amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 22 22:32:04 2018 InstallationDate: Installed on 2018-07-30 (84 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (4 days ago) ** Affects: nvidia-gra
[Bug 253119] Re: PPA packages do not show a changelog in update-manager
Thanks for the persistence and all the work to bring this feature to fruition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/253119 Title: PPA packages do not show a changelog in update-manager To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/253119/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559368] Re: gnome-calendar crashed with SIGSEGV in gtk_widget_translate_coordinates()
*** This bug is a duplicate of bug 1552940 *** https://bugs.launchpad.net/bugs/1552940 bug #1552940 returns "cannot be found" error. I presume it is not visible so please can someone make it visible? Perhaps I should report a but against the Apport retracing service. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559368 Title: gnome-calendar crashed with SIGSEGV in gtk_widget_translate_coordinates() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1559368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559368] [NEW] gnome-calendar crashed with SIGSEGV in gtk_widget_translate_coordinates()
Public bug reported: $ lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 $ apt-cache policy gnome-calendar gnome-calendar: Installed: 3.19.92-0ubuntu2 Candidate: 3.19.92-0ubuntu2 Version table: *** 3.19.92-0ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status What you expected to happen: Select "Calendar Settings" more than once opens dialogue. What happened instead: Consistently crashes the second time I access the "Calendar Settings" option. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: gnome-calendar 3.19.92-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 19 01:17:57 2016 ExecutablePath: /usr/bin/gnome-calendar InstallationDate: Installed on 2014-08-02 (594 days ago) InstallationMedia: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/gnome-calendar --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7efefef81f50 : mov(%r14),%rax PC (0x7efefef81f50) ok source "(%r14)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-calendar StacktraceTop: gtk_widget_translate_coordinates () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_event_controller_handle_event () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: gnome-calendar crashed with SIGSEGV in gtk_widget_translate_coordinates() UpgradeStatus: Upgraded to xenial on 2016-03-14 (4 days ago) UserGroups: family libvirtd paul sudo ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559368 Title: gnome-calendar crashed with SIGSEGV in gtk_widget_translate_coordinates() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1559368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1483707] [NEW] Rhythmbox crashes in source_rhythmbox.py during apport reporting of a bug
Public bug reported: Description:Ubuntu 15.04 Release:15.04 rhythmbox: Installed: 3.1-1ubuntu3 Candidate: 3.1-1ubuntu3 Version table: *** 3.1-1ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status I expect to be prompted to report a bug during a crash, instead nothing happens. The crash report in /var/crash/_usr_lib_rhythmbox_rhythmbox-metadata.500.upload is zero bytes In $HOME/.cache/upstart/ I have file update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log.1.gz attached ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Attachment added: "update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log" https://bugs.launchpad.net/bugs/1483707/+attachment/4442891/+files/update-notifier-crash-_var_crash__usr_lib_rhythmbox_rhythmbox-metadata.500.crash.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483707 Title: Rhythmbox crashes in source_rhythmbox.py during apport reporting of a bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1483707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282997] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
I've traced the gst_base_parse_push_frame() function to the GstBaseParse class in libgstreamer1.0-0 ** Package changed: rhythmbox (Ubuntu) => gstreamer1.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282997 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1282997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1282997] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
** This bug is no longer a duplicate of private bug 1234934 ** This bug has been marked a duplicate of bug 1286563 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug is no longer a duplicate of bug 1286563 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1282997 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1282997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286563] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
*** This bug is a duplicate of bug 1282997 *** https://bugs.launchpad.net/bugs/1282997 ** This bug has been marked a duplicate of bug 1282997 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286563 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1286563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286563] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
*** This bug is a duplicate of bug 1282997 *** https://bugs.launchpad.net/bugs/1282997 ** This bug is no longer a duplicate of private bug 1234934 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286563 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1286563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292869] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
*** This bug is a duplicate of bug 1282997 *** https://bugs.launchpad.net/bugs/1282997 ** This bug has been marked a duplicate of bug 1286563 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug is no longer a duplicate of bug 1282997 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug has been marked a duplicate of bug 1282997 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug is no longer a duplicate of bug 1282997 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug has been marked a duplicate of bug 1282997 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug is no longer a duplicate of bug 1286563 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() ** This bug has been marked a duplicate of bug 1282997 rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292869 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1292869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292869] Re: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
** This bug is no longer a duplicate of private bug 1234934 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292869 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1292869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467282] [NEW] Nvidia-304-Updates no longer working for Nvidia 7600 GS card
Public bug reported: I have a Nivida Geforce 7600 GS on a machine used infrequently. A month of so ago it worked fine, recent updates have broken the graphics drivers. It can boot to the login screen which looks OK, but is almost unresponsive bringing up a desktop. Even for a guest login. Once loaded, graphics are corrupt with icons etc showing mostly random coloured pixels. All package are up to date. Purging all the nvidia drivers and using the nouveau drivers works fine, enabling a normal login. I have checked the nvidia site and this driver is the most recent that supports my graphics card. Ubuntu 14.04.2 LTS nvidia-304: 304.125-0ubuntu0.0.1 http://askubuntu.com/questions/592095/nvidia-304-updates-broken-on- ubuntu-14-04-2 ** Affects: nvidia-graphics-drivers-304-updates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467282 Title: Nvidia-304-Updates no longer working for Nvidia 7600 GS card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1467282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1422484] Re: Apache hangs/crash while running OwnCloud 8.0.0
I've been having the same issue and am now waiting to see if purging php5-apcu helps. When apache stops responding, it has maxed out on threads and I get this message in error.log: [mpm_prefork:error] [pid 7628] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting I also have seen a apc related error: PHP Warning: apc_store(): GC cache entry 'oc558dd98d33/AutoloaderOC_User_Interface' was on gc-list for 3602 seconds in /var/www/owncloud/lib/private/memcache/apc.php on line 21 Killing a few threads allowed me to get to /server-status on the server which showed the threads were all in "Sending Reply" states responding to owncloud/status.php requests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1422484 Title: Apache hangs/crash while running OwnCloud 8.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-apcu/+bug/1422484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304083] [NEW] rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame()
Public bug reported: Not playing audio at the time, just searching tracks. Application was still running when the bug reporter kicked into action. It appeared to close normally. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 7 23:28:49 2014 ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata InstallationDate: Installed on 2010-06-09 (1398 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp SegvAnalysis: Segfault happened at: 0x7fde9c04fc4f: mov%r12,0x48(%rax) PC (0x7fde9c04fc4f) ok source "%r12" ok destination "0x48(%rax)" (0x0048) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: rhythmbox StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_base_parse_push_frame () from /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() UpgradeStatus: Upgraded to trusty on 2014-03-29 (9 days ago) UserGroups: adm admin broadhead cdrom dialout libvirtd lpadmin mythtv plugdev sambashare ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304083 Title: rhythmbox-metadata crashed with SIGSEGV in gst_base_parse_push_frame() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1304083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242886] Re: Regression: List boxes do not properly resize when given "height"
Received the fix when I updated trusty today. The list function now works correctly. Many thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242886 Title: Regression: List boxes do not properly resize when given "height" To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1242886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1303958] [NEW] gjs-console crashed with SIGSEGV in JS_NewFunction()
Public bug reported: Happened on fresh reboot, at initial login. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gjs 1.39.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Apr 7 19:40:13 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gjs-console InstallationDate: Installed on 2014-02-24 (41 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140218) ProcCmdline: /usr/bin/gjs /usr/share/org.gnome.Weather.Application/org.gnome.Weather.Application SegvAnalysis: Segfault happened at: 0x7fd6b7da8704: mov(%rdi),%rax PC (0x7fd6b7da8704) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gjs StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 JS_NewFunction(JSContext*, int (*)(JSContext*, unsigned int, JS::Value*), unsigned int, unsigned int, JSObject*, char const*) () from /usr/lib/x86_64-linux-gnu/libmozjs-24.so.0 gjs_init_class_dynamic () from /usr/lib/libgjs.so.0 Title: gjs-console crashed with SIGSEGV in JS_NewFunction() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace trusty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303958 Title: gjs-console crashed with SIGSEGV in JS_NewFunction() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1303958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247137] Re: zenity 3.8 --list outputs first answer twice separated by a pipe
** Bug watch added: GNOME Bug Tracker #698683 https://bugzilla.gnome.org/show_bug.cgi?id=698683 ** Also affects: zenity via https://bugzilla.gnome.org/show_bug.cgi?id=698683 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247137 Title: zenity 3.8 --list outputs first answer twice separated by a pipe To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/1247137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267788] Re: double click in list print two time the selected item
*** This bug is a duplicate of bug 1247137 *** https://bugs.launchpad.net/bugs/1247137 ** This bug has been marked a duplicate of bug 1247137 zenity 3.8 --list outputs first answer twice separated by a pipe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267788 Title: double click in list print two time the selected item To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1267788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1247137] Re: zenity 3.8 --list outputs first answer twice separated by a pipe
This is fixed in upstream commit: 7c234ed9b71d5f009abff509ef2bf576f61a0cbb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247137 Title: zenity 3.8 --list outputs first answer twice separated by a pipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1247137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 665932] Re: boot stops at resume: libgcrypt 1.4.5 for over 20 seconds
I'm dual booting Debian (jessie) and Ubuntu. I recently reinstalled Ubuntu to 13.10 and lost the ability to boot Debian in the process. Debian just hung for ever at the "'resume : libgcrypt " line. I booted from a live USB stick, mounted sys/dev/proc, chrooted, reinstalled grub then modifed /usr/share/initramfs-tools/hooks/resume as suggested and ran "update-initramfs -u". This has fixed boot for Debian. Previously, following the steps without the resume and update-initramfs bits did not fix the boot. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/665932 Title: boot stops at resume: libgcrypt 1.4.5 for over 20 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt11/+bug/665932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105774] Re: hda-intel: spurious response and [pulseaudio] module-udev-detect.c: inotify_init1() failed: Too many open files
In case it helps, my output from "pulseaudio -vvv" too. ** Attachment added: "Output from pulseaudio -vvv" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1105774/+attachment/3505455/+files/pulseaudio-vvv.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105774 Title: hda-intel: spurious response and [pulseaudio] module-udev-detect.c: inotify_init1() failed: Too many open files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1105774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105774] Re: hda-intel: spurious response and pulseaudio fails to start with no reason
** Attachment added: "Hardware list from lscpi" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1105774/+attachment/3501241/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105774 Title: hda-intel: spurious response and pulseaudio fails to start with no reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1105774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1105774] Re: hda-intel: spurious response and pulseaudio fails to start with no reason
I have a similar if not the same problem. It started around the same time. I do not use a kde desktop, only unity but I do run some kde apps e.g. kaffeine. However, I do not know if it is related to use of these. The indicator-sound and system-settings->audio controls are greyed out but I can play sounds. Per session pulse audio will not start for me. If I log out and try another user, their audio is fine. So is lighdm. If I log in again, my audio is still broken. I have tried removing user pulse audio files located in my home directory and /tmp. I have also made sure all processed owned by me are stopped when I logout. However, only a reboot fixes the problem. If I try to start pulse auto manually using "start-pulseaudio-x11" I get this error at the command line: Connection failure: Connection refused pa_context_connect() failed: Connection refused And this text in /var/log/syslog: Jan 26 12:52:05 hagrid rtkit-daemon[2970]: Successfully made thread 28324 of process 28324 (n/a) owned by '500' high priority at nice level -11. Jan 26 12:52:05 hagrid rtkit-daemon[2970]: Supervising 1 threads of 1 processes of 1 users. Jan 26 12:52:05 hagrid pulseaudio[28324]: [pulseaudio] module-udev-detect.c: inotify_init1() failed: Too many open files Jan 26 12:52:05 hagrid pulseaudio[28324]: [pulseaudio] module.c: Failed to load module "module-udev-detect" (argument: ""): initialization failed. Jan 26 12:52:05 hagrid pulseaudio[28324]: [pulseaudio] main.c: Module load failed. Jan 26 12:52:05 hagrid pulseaudio[28324]: [pulseaudio] main.c: Failed to initialise daemon. Jan 26 12:52:05 hagrid pulseaudio[28321]: [pulseaudio] main.c: Daemon startup failed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1105774 Title: hda-intel: spurious response and pulseaudio fails to start with no reason To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1105774/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
How do I change this bug report to a back port request? ** Tags added: backport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
This bug is fixed in gstreamer 1.0 available from https://launchpad.net /~gstreamer-developers/+archive/ppa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true.
** Description changed: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true. To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true.
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true. To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true.
The proposed release fixed this bug and installs cleanly. I tested using this method: # check the indicator is not running ps -ef | grep indicator-weather paul 12866 9323 0 11:32 pts/800:00:00 grep indicator-weather # find a suitable test process PID that does not exist but where the digits are part of an existing process PID ls /proc | grep 42 1242 2429 8442 # create a false indicator pid file with that pid echo "42" > /tmp/indicator-weather-$UID.pid # start the indicator # with the bug version, the indicator will not start indicator-weather /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject Another instance of this program is already running # with the new versions, the indicator starts fine indicator-weather # Attempting to start a second instance new version does fails as it should -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true. To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true.
I have confirmed Neal's experience with the package failing to install, with the same error message. I can't quite work my head around what is happening but if you build a .deb from the new source, the file indicator-weather.gschema.xml is already located in the correct directory and so the copy in debian/postinst fails and is probably not needed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather refuses to start, saying "Another instance of this program is already running" when that is not true. To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
OK, I've added the upstream bug report. Thanks again for your help. ** Bug watch added: GNOME Bug Tracker #678804 https://bugzilla.gnome.org/show_bug.cgi?id=678804 ** Also affects: gstreamer via https://bugzilla.gnome.org/show_bug.cgi?id=678804 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/gstreamer/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
[paul@hagrid ~]$ gst-launch-0.10 playbin uri=file:///home/music/Kate\ Bush/50\ Words\ for\ Snow/03\ -\ Misty.flac Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstPulseSinkClock Got EOS from element "playbin0". Execution ended after 103267376918 ns. Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ... Thanks for the response Iain. Unfortunately, playback stops at exactly the same point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
apt-cache policy rhythmbox rhythmbox: Installed: 2.97-1ubuntu1~precise1 Candidate: 2.97-1ubuntu1~precise1 Version table: *** 2.97-1ubuntu1~precise1 0 500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status 2.96-0ubuntu4 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages Thanks for the response Mantas, unfortunately the track still stops at the same point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
I've just re-extracted the track from the audio CD, the new file skips in exactly the same place. The track plays fine from the audio CD. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
The file also play fine using rhythmbox in a lucid virtual machine. lsb_release -rd Description:Ubuntu 10.04.4 LTS Release:10.04 apt-cache policy rhythmbox rhythmbox: Installed: 0.12.8-0ubuntu7 Candidate: 0.12.8-0ubuntu7 Version table: *** 0.12.8-0ubuntu7 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 0.12.8-0ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid/main Packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] Re: Playback stops for particular track after 1 min 41 sec (repeatable)
** Attachment added: "rblog" https://bugs.launchpad.net/bugs/1008605/+attachment/3175094/+files/rblog ** Description changed: lsb_release -rd Description: Ubuntu 12.04 LTS Release: 12.04 apt-cache policy rhythmbox rhythmbox: - Installed: 2.96-0ubuntu4 - Candidate: 2.96-0ubuntu4 - Version table: - *** 2.96-0ubuntu4 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.96-0ubuntu4 + Candidate: 2.96-0ubuntu4 + Version table: + *** 2.96-0ubuntu4 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages + 100 /var/lib/dpkg/status The track should play to completion, instead the track stops playing. I have verified the track is not corrupted as it plays fine using /usr/bin/play and verified it using: - flac -t 3_-_Misty.flac + flac -t 3_-_Misty.flac flac 1.2.1, Copyright (C) 2000,2001,2002,2003,2004,2005,2006,2007 Josh Coalson flac comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. Type `flac' for details. 3_-_Misty.flac: ok The same happens on a different machine running the same version of Ubuntu and rhythmbox with just this file in a new music database. I have attached the output from rhythmbox --debug, selecting the track and - skipping to just before the problem, then exiting rhythmbox. + skipping to just before the problem, then exiting rhythmbox. If I skip + past the position of the problem the track plays to completion. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Mon Jun 4 17:35:03 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-04-28 (37 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008605] [NEW] Playback stops for particular track after 1 min 41 sec (repeatable)
Public bug reported: lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 apt-cache policy rhythmbox rhythmbox: Installed: 2.96-0ubuntu4 Candidate: 2.96-0ubuntu4 Version table: *** 2.96-0ubuntu4 0 500 http://gb.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status The track should play to completion, instead the track stops playing. I have verified the track is not corrupted as it plays fine using /usr/bin/play and verified it using: flac -t 3_-_Misty.flac flac 1.2.1, Copyright (C) 2000,2001,2002,2003,2004,2005,2006,2007 Josh Coalson flac comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. Type `flac' for details. 3_-_Misty.flac: ok The same happens on a different machine running the same version of Ubuntu and rhythmbox with just this file in a new music database. I have attached the output from rhythmbox --debug, selecting the track and skipping to just before the problem, then exiting rhythmbox. If I skip past the position of the problem the track plays to completion. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Mon Jun 4 17:35:03 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-04-28 (37 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008605 Title: Playback stops for particular track after 1 min 41 sec (repeatable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1008605/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 995435] Re: Zenity --list uses 100%cpu and does nothing
The packages in proposed fix the problem for me. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/995435 Title: Zenity --list uses 100%cpu and does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/995435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather leaves .pid file in /tmp and will not restart
Looks like this fix didn't make it into precise. Any chance it could be updated? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather leaves .pid file in /tmp and will not restart To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 949992] Re: Upgrade from Lucid to Precise results in broken grub configuration
I just had the same result using a clone of a Lucid VM. I was prompted part way though the process to allow grub install. A single tick box was present, un-ticked, asking if I didn't want to install grub. Leaving un-ticked and clicking forward did not work, nothing happened after waiting for sometime. So I ticked the box and continued assuming it would be OK. This was a test upgrade on a clone VM so I can repeat the process if required. I'm off to manually fix the problem and continue testing... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/949992 Title: Upgrade from Lucid to Precise results in broken grub configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/949992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 932781] Re: [x-updates] Nvidia 295.20 regression - Gnome Shell becomes crashy
295.33-0ubuntu1~oneiric~xup1 has just been release which seems to have fixed the gnome3 crashing problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932781 Title: [x-updates] Nvidia 295.20 regression - Gnome Shell becomes crashy To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/932781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566856] Re: Invalid SDL_ACTIVEEVENT events generated on mouse clicks when compiz enabled
Description:Ubuntu 11.10 Release:11.10 compiz: Installed: 1:0.9.6+bzr20110929-0ubuntu6.1 Candidate: 1:0.9.6+bzr20110929-0ubuntu6.1 Version table: *** 1:0.9.6+bzr20110929-0ubuntu6.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.6+bzr20110929-0ubuntu3 0 I upgraded to oneiric only recently. The test program works as it should on oneiric. I guess the problem had been fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/566856 Title: Invalid SDL_ACTIVEEVENT events generated on mouse clicks when compiz enabled To manage notifications about this bug go to: https://bugs.launchpad.net/compiz-core/+bug/566856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather leaves .pid file in /tmp and will not restart
Much better. Thanks for the quick response. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather leaves .pid file in /tmp and will not restart To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather leaves .pid file in /tmp and will not restart
Vadim. Thanks for commiting the change but you have not used my patch. In fact, I think the change you have made instead breaks the pid detection even more. Please could you have another look at my patch and how you have made the change. My patch uses the "ls -1" to list just the file names, one per line, and the regex "$XX^" (i.e starting and ending) to match exactly files. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather leaves .pid file in /tmp and will not restart To manage notifications about this bug go to: https://bugs.launchpad.net/weather-indicator/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] Re: indicator-weather leaves .pid file in /tmp and will not restart
I've now checked the source code. Unfortunatly, I did not check the contents of the .pid file before deleting it. However, I can see from my directory listing that the length was only 3 characters. Looking at the pid checking code, perhaps the 3 characters matched in part some other process number. I've attached a potential patch to avoid this. ** Attachment added: "patch" https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/926433/+attachment/2712418/+files/patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather leaves .pid file in /tmp and will not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 926433] [NEW] indicator-weather leaves .pid file in /tmp and will not restart
Public bug reported: Description:Ubuntu 11.10 Release:11.10 indicator-weather: Installed: 11.05.31-0ubuntu2.1 Candidate: 11.05.31-0ubuntu2.1 Version table: *** 11.05.31-0ubuntu2.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric-updates/universe amd64 Packages 100 /var/lib/dpkg/status 11.05.31-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages Expect the indicator to start when run, but it does not but gives the following error message: /usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed import gobject._gobject Another instance of this program is already running At some stage I assume the indicator crashed and left a file in /tmp called indicator-weather-500.pid. The log file ~/.cache/indicator- weather.log shows extra messages, just that another instances is running. I checked the process list and no instance was running. Once the .pid file had been deleted, the indicator started and ran as normal. ** Affects: indicator-weather (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926433 Title: indicator-weather leaves .pid file in /tmp and will not restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/926433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913574] Re: Recent messages are repeated each time I login
*** This bug is a duplicate of bug 882572 *** https://bugs.launchpad.net/bugs/882572 ** This bug has been marked a duplicate of bug 882572 The same post are showing up in feed multiple times -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913574 Title: Recent messages are repeated each time I login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/913574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913574] Re: Recent messages are repeated each time I login
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913574 Title: Recent messages are repeated each time I login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/913574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913574] [NEW] Recent messages are repeated each time I login
Public bug reported: Simply that each time I login, old messges are repeated. Some from hours ago. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gwibber 3.2.1-0ubuntu1.3 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Jan 8 23:23:07 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gwibber UpgradeStatus: Upgraded to oneiric on 2012-01-07 (1 days ago) ** Affects: gwibber (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug apport-lpi oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913574 Title: Recent messages are repeated each time I login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/913574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623144] Re: chkutmp assert failure: *** stack smashing detected ***: ./chkutmp terminated
I've also just encountered this bug on Lucid 10.04LTS. Can the importance be bumped please. Surely a crash in a security tool is very high importance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/623144 Title: chkutmp assert failure: *** stack smashing detected ***: ./chkutmp terminated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/623144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455461] Re: Sound Juicer depends on deprecated libmusicbrainz4
The version in lucid-proposed is working fine for me. Thanks very much to everyone for their efforts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455461 Title: Sound Juicer depends on deprecated libmusicbrainz4 To manage notifications about this bug go to: https://bugs.launchpad.net/sound-juicer/+bug/455461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455461] Re: Sound Juicer depends on deprecated libmusicbrainz4
Reading SRU page https://wiki.ubuntu.com/StableReleaseUpdates it appears that's all us users can do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455461 Title: Sound Juicer depends on deprecated libmusicbrainz4 To manage notifications about this bug go to: https://bugs.launchpad.net/sound-juicer/+bug/455461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 455461] Re: Sound Juicer depends on deprecated libmusicbrainz4
SRU: Here is a stab at following the Stable Release Updates process: 1) The bug is fixed in the current development release. 2) This bug prevents CD contents from being looked up from the Music Brainz service leaving the user to manually enter track information. This is a major inconvenience to the user and mis-lead me to attempt uploading track information that could cause duplications in the Music Brainz service. 3) The fix outlined about is a simple rebuild against a non-depreciated version of the Music Brainz API - versions outlined above. 4) I have used the above patch to build my own version of the package which works successfully. TEST CASE: 5) When using the gnome desktop, Insert a music CD and wait for sound-juicer to start. IT wil fail to look up the track list. 5) I have being using the patch package for several weeks without any adverse effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/455461 Title: Sound Juicer depends on deprecated libmusicbrainz4 To manage notifications about this bug go to: https://bugs.launchpad.net/sound-juicer/+bug/455461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566856] Re: Invalid SDL_ACTIVEEVENT events generated on mouse clicks when compiz enabled
** Changed in: compiz (Ubuntu) Status: Incomplete => Opinion ** Changed in: compiz (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/566856 Title: Invalid SDL_ACTIVEEVENT events generated on mouse clicks when compiz enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/566856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 566856] Re: Invalid SDL_ACTIVEEVENT events generated on mouse clicks when compiz enabled
I'm sticking with lucid for now on my desktop machine so can't test Natty on that. Driver issues mean I can't boot from alive disk either. However, on a different machine running Natty the test program shows the correct behaviour. This is for both the unity interface and Gnome classic. However, user settings no longer provides control of compiz so I have no idea if compiz is enabled or off. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/566856 Title: Invalid SDL_ACTIVEEVENT events generated on mouse clicks when compiz enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/566856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 481379] Re: Eternal Lands crash with gm965
> The bug is still occurring, with desktop effects turned off, #poor_man=1 and #use_animation_program= 0. Hi Karl. You must either be experiencing a different bug or you have not set "#use_animation_program= 0". The original bug was a crash in the function "cal_render_actor_shader()". That function is only ever called if "#use_animation_program= 1". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/481379 Title: Eternal Lands crash with gm965 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
Philippe Rouquier has fixed the crash (in my case at least) in the upstream version. I've attached a patch based on the diff between the current Ubuntu Lucid version (2.30-2) and the series of commits by Philippe Rouquier. These commits are: http://git.gnome.org/browse/brasero/commit/?h=gnome-2-30&id=f031e1ee921886ef2a0f50a936cf939a9d614463 http://git.gnome.org/browse/brasero/commit/?h=gnome-2-30&id=b1b8ae5c0bf918503cd10380c9634d814f9f7a23 http://git.gnome.org/browse/brasero/commit/?h=gnome-2-30&id=4a34a5129d0d9d3a2d155b9f0c53cb01c68f87c0 ** Patch added: "Fix from 3 upstream commits" http://launchpadlibrarian.net/52387776/brasero.working.lucid.patch -- sound-juicer, rhythmbox, nautilus crash at audio CD insertion https://bugs.launchpad.net/bugs/501207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
** Patch added: "Modified f031e1ee921886ef2a0f50a936cf939a9d614463 patch (working)" http://launchpadlibrarian.net/52288613/working.patch -- sound-juicer, rhythmbox, nautilus crash at audio CD insertion https://bugs.launchpad.net/bugs/501207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
I've commented on the upstream bug tracker. The patch did not fix the crash for me but a simple additional check with the patch did fix the crash. Looks like we getting close. As before, I still get the "I/O error" messages. I've attached the upstream patch and my hacked version that works for me. ** Patch added: "Original upstream patch" http://launchpadlibrarian.net/52288576/f031e1ee921886ef2a0f50a936cf939a9d614463.patch -- sound-juicer, rhythmbox, nautilus crash at audio CD insertion https://bugs.launchpad.net/bugs/501207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
In the above debug log, there are some values, one crucial value is that of num in the brasero_medium_read_CD_TEXT() function that calls _next_CD_TEXT_pack() where the crash happens. This sets the assumed size of the array who's access is causing the SEGV. The value is 954437176 probably more that actually allocated. On another machine running the same version of brasero, the value is 0. If I prevent the call to _next_CD_TEXT_pack() then the crash does not happen and the applications appear to function as expected. I'm not sure what CD_TEXT actually is but the audio CD I have been trying appears to no use it. I still get the "I/O error" messages of course. : [85642.694961] sr 0:0:1:0: [sr0] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [85642.694968] sr 0:0:1:0: [sr0] Sense Key : Illegal Request [current] [85642.694974] sr 0:0:1:0: [sr0] Add. Sense: Illegal mode for this track [85642.694982] sr 0:0:1:0: [sr0] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00 [85642.694994] end_request: I/O error, dev sr0, sector 0 I think there is a low level problem with the CD driver that needs fixing but the crash in brasero could possibly be prevented. -- sound-juicer, rhythmbox, nautilus crash at audio CD insertion https://bugs.launchpad.net/bugs/501207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
I've compile brasero-2.30.1 from the sourcepackage, installed and done a ldconfig. When I run sound-juicer through gdm I get the attached debuglog output. Does this help? I'll happily do more to help fix this. ** Attachment added: "debuglog" http://launchpadlibrarian.net/50756786/debuglog -- sound-juicer, rhythmbox, nautilus crash at audio CD insertion https://bugs.launchpad.net/bugs/501207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 501207] Re: sound-juicer, rhythmbox, nautilus crash at audio CD insertion
Description: Ubuntu 10.04 LTS Release: 10.04 brasero: Installed: 2.30.1-0ubuntu2 Candidate: 2.30.1-0ubuntu2 Version table: *** 2.30.1-0ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2.30.0-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ lucid/main Packages Linux hagrid 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux I have a PIONEER DVR-218L (aka Pioneer DVR-S18L) with a Intel DH55HC motherboard and Intel Core i3 CPU. Again, sound-juicer, rhythmbox, nautilus crash at audio CD insertion. Both vlc and kaffeine can play files from the audio cd. Other CD/DVD read/write works fine. example dmesg output sound-juicer[3173]: segfault at 1fe4002 ip 7f89178bcbef sp 7f890da03a60 error 4 in libbrasero-media.so.0.2.0[7f89178aa000+23000 [ 883.754312] nautilus[3182]: segfault at 274a008 ip 7f6604cd8f20 sp 7f65f5864a20 error 4 in libbrasero-media.so.0.2.0[7f6604cc6000+23000] [ 1645.522902] rhythmbox[3405]: segfault at 34d6008 ip 7ff00b331dfd sp 7ff009480a40 error 4 in libbrasero-media.so.0.2.0[7ff00b31f000+23000] -- sound-juicer, rhythmbox, nautilus crash at audio CD insertion https://bugs.launchpad.net/bugs/501207 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" http://launchpadlibrarian.net/46384448/WifiSyslog.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/46384421/PciMultimedia.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/46384443/UdevLog.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/46384441/UdevDb.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/46384434/ProcModules.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/46384429/ProcInterrupts.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/46384423/ProcCpuinfo.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 557266] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/46384411/IwConfig.txt -- [Radeon kernel module] drmRadeonCmdBuffer: -22. Kernel failed to parse or rejected command stream https://bugs.launchpad.net/bugs/557266 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs