[Dx-packages] [Bug 1530807] Re: Bluetooth cannot be activated on several devices
Maybe some of the issues here are a duplicate of bug #1546137 ? -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1530807 Title: Bluetooth cannot be activated on several devices Status in The Avila project: In Progress Status in Canonical System Image: Fix Committed Status in Canonical Pocket Desktop: Confirmed Status in indicator-bluetooth package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Using RC proposed 04/01/2016 bluetooth cannot be enabled. Tested on a nexus 7. Expected behavior: Bluetooth slider is moved to on Bluetooth activates Available devices appear in the list Experienced behavior: Bluetooth slider is moved to on Activity spinners appear Bluetooth slider moves to off. To manage notifications about this bug go to: https://bugs.launchpad.net/avila/+bug/1530807/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1548479] [NEW] unity8 clock gui menu crashed
Public bug reported: opened unity8 kin terminal left clicked clock on gui and unity 8 crashed. ProblemType: RecoverableProblem DistroRelease: Ubuntu 16.04 Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BadURL: appid://com.ubuntu.clock/clock/current-user-version CurrentDesktop: Unity Date: Mon Feb 22 13:25:44 2016 DuplicateSignature: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2016-02-09 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo modified.conffile..etc.xdg.autostart.indicator.datetime.desktop: [modified] mtime.conffile..etc.xdg.autostart.indicator.datetime.desktop: 2016-02-10T20:02:56.836372 ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-recoverableproblem xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1548479 Title: unity8 clock gui menu crashed Status in indicator-datetime package in Ubuntu: New Bug description: opened unity8 kin terminal left clicked clock on gui and unity 8 crashed. ProblemType: RecoverableProblem DistroRelease: Ubuntu 16.04 Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BadURL: appid://com.ubuntu.clock/clock/current-user-version CurrentDesktop: Unity Date: Mon Feb 22 13:25:44 2016 DuplicateSignature: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2016-02-09 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo modified.conffile..etc.xdg.autostart.indicator.datetime.desktop: [modified] mtime.conffile..etc.xdg.autostart.indicator.datetime.desktop: 2016-02-10T20:02:56.836372 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1548479/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1548479] Re: unity8 clock gui menu crashed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1548479 Title: unity8 clock gui menu crashed Status in indicator-datetime package in Ubuntu: New Bug description: opened unity8 kin terminal left clicked clock on gui and unity 8 crashed. ProblemType: RecoverableProblem DistroRelease: Ubuntu 16.04 Package: indicator-datetime 15.10+16.04.20160129-0ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 BadURL: appid://com.ubuntu.clock/clock/current-user-version CurrentDesktop: Unity Date: Mon Feb 22 13:25:44 2016 DuplicateSignature: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service:url-dispatcher-bad-url ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service InstallationDate: Installed on 2016-02-09 (13 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=en_US.UTF-8 LANGUAGE=en_US XDG_RUNTIME_DIR= SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo modified.conffile..etc.xdg.autostart.indicator.datetime.desktop: [modified] mtime.conffile..etc.xdg.autostart.indicator.datetime.desktop: 2016-02-10T20:02:56.836372 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1548479/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
** Changed in: qtlocation-opensource-src (Debian) Status: Unknown => New -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Debian: New Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
Empathy already supports geoclue 2.0 but there is a patch reverting this. Fixing this for empathy is as easy as dropping the patch and readding the (build)-dependencies -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1543617] Re: InputSources should have an explicit default
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1543617 Title: InputSources should have an explicit default Status in Canonical System Image: New Status in accountsservice package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: The AccountsService package rolls the org.freedesktop.Accounts.User.xml schema, which comes with a default, empty InputSources. Mir defaults to “en”. Maybe we should set this value to “en” so that there's a canonical way of figuring out what InputSource to use. Additionally, if a vendor wants “no” to be the default, it could make sense to just override this schema default value. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1543617/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtlocation-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: empathy (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webkitgtk (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-geoip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1389336] Re: Use geoclue-2.0
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libunity-webapps (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity-webapps in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in empathy package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in libunity-webapps package in Ubuntu: Confirmed Status in qtlocation-opensource-src package in Ubuntu: Confirmed Status in ubuntu-geoip package in Ubuntu: Confirmed Status in webkitgtk package in Ubuntu: Confirmed Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
** Also affects: compiz-plugins-main (Ubuntu) Importance: Undecided Status: New ** Changed in: compiz-plugins-main (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of DX Packages, which is subscribed to compiz-plugins-main in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock Status in Unity: Fix Released Status in Unity 7.1 series: Fix Released Status in compiz-plugins-main package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Bug description: I run a dual monitor configuration, with one portrait and one landscape. I nearly always have multiple applications open in multiple windows across both monitors and all virtual desktops. When I lock the screen and then unlock, my application windows will move from their original position. Sometimes they are in completely random positions; Other times they seem to get the monitors confused, and rather than being in the top half of the portrait monitor they are on the top half of the landscape monitor; Sometimes it is only a new desktop, but the monitor position is the same; Sometimes it is the same desktop, but on the other monitor. Description: Ubuntu 13.10 Release: 13.10 What I expect to happen: When I unlock my computer, all the windows are in the same position on the same monitor and desktop as I left them. What actually happens: When I unlock my computer, some or all of the windows have been changed to a random position on a random monitor and/or desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1527848] Re: Indicator-Datetime always shows UTC time for any online calendar added to evolution (Unity7, Xenial)
** Description changed: My timezone is set to GMT+5:30 (Kolkata, India) from indicator datetime settings. But when I add a online google calendar in Evolution, events (which has start time and end time) are appearing as UTC time. However in evolution, its all nice and evolution does respect my timezone. How to reproduce: 1. Set google calendar timezone to match your timezone from google calendar settings (web). 2. From web interface, add a event with time into that calendar. Then copy its private ical address. 3. Open evolution. Add that calendar from new->calendar->on the web. 4. reboot. What should happen? If a event starts from 5 PM, indicator-datetime should reflect that. What is happening? indicator-datetime shows every event starting at UTC time; i.e, in my - case 5.30 hours behind! + case 5.30 hours leading! Screenshot: http://i.imgur.com/gPisVnl.png Note: It seems it only happens for online calendars. Locally created events are ok. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1527848 Title: Indicator-Datetime always shows UTC time for any online calendar added to evolution (Unity7, Xenial) Status in indicator-datetime package in Ubuntu: New Bug description: My timezone is set to GMT+5:30 (Kolkata, India) from indicator datetime settings. But when I add a online google calendar in Evolution, events (which has start time and end time) are appearing as UTC time. However in evolution, its all nice and evolution does respect my timezone. How to reproduce: 1. Set google calendar timezone to match your timezone from google calendar settings (web). 2. From web interface, add a event with time into that calendar. Then copy its private ical address. 3. Open evolution. Add that calendar from new->calendar->on the web. 4. reboot. What should happen? If a event starts from 5 PM, indicator-datetime should reflect that. What is happening? indicator-datetime shows every event starting at UTC time; i.e, in my case 5.30 hours leading! Screenshot: http://i.imgur.com/gPisVnl.png Note: It seems it only happens for online calendars. Locally created events are ok. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1527848/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1542627] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1542782 *** https://bugs.launchpad.net/bugs/1542782 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1542782, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1542627/+attachment/4565076/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1542627/+attachment/4565078/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1542627/+attachment/4565080/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1542627/+attachment/4565081/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1542627/+attachment/4565082/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1542627/+attachment/4565083/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1542627/+attachment/4565084/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1542782 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1542627 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: crashes every time on boot ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libunity9 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Feb 6 12:06:08 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2016-02-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7f5eb8b56300 : movzbl 0xc0(%rdi),%eax PC (0x7f5eb8b56300) ok source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxsf vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1542627/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1471087] Re: Battery power indicator shows incorrect battery percentage when fully charged
This might be a duplicate of bug 1473428. Unfortunately neither report contains steps to reproduce the problem. -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1471087 Title: Battery power indicator shows incorrect battery percentage when fully charged Status in indicator-power package in Ubuntu: New Bug description: Ubuntu 15.04 indicator-power: Installed: 12.10.6+15.04.20150402-0ubuntu1 Candidate: 12.10.6+15.04.20150402-0ubuntu1 Version table: *** 12.10.6+15.04.20150402-0ubuntu1 0 500 http://kr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Power indicator currently showing 70%, however, battery is fully charged and running on AC power. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-power 12.10.6+15.04.20150402-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 2 22:14:47 2015 InstallationDate: Installed on 2015-06-20 (12 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: indicator-power UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1471087/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1539853] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': corrupted double-linked list: 0x0000000001fdb260 ***
** Information type changed from Private to Public -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1539853 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': corrupted double-linked list: 0x01fdb260 *** Status in libunity package in Ubuntu: Confirmed Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': corrupted double-linked list: 0x01fdb260 *** CrashCounter: 1 CurrentDesktop: Unity Date: Sat Jan 30 01:39:09 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2016-01-25 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=1, fmt=fmt@entry=0x7f687bba1128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=0x1fdb240, str=0x7f687bb9d25d "corrupted double-linked list", action=1) at malloc.c:4965 _int_realloc (av=av@entry=0x7f687bdd4c00 , oldp=oldp@entry=0x1fdb240, oldsize=oldsize@entry=32, nb=nb@entry=48) at malloc.c:4265 __GI___libc_realloc (oldmem=0x1fdb250, bytes=32) at malloc.c:3023 g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': corrupted double-linked list: 0x01fdb260 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1539853/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1541084] Re: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden()
*** This bug is a duplicate of bug 1542782 *** https://bugs.launchpad.net/bugs/1542782 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1542782, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1541084/+attachment/4562507/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1541084/+attachment/4562509/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1541084/+attachment/4562512/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1541084/+attachment/4562513/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1541084/+attachment/4562514/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1541084/+attachment/4562515/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1541084/+attachment/4562516/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1542782 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1541084 Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() Status in libunity package in Ubuntu: New Bug description: sometimes can i see this crash after closing q4wine ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libunity9 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Tue Feb 2 20:31:16 2016 ExecutablePath: /usr/bin/unity-scope-loader InstallationDate: Installed on 2015-11-11 (82 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (2015) ProcCmdline: /usr/bin/unity-scope-loader applications/applications.scope applications/scopes.scope commands.scope SegvAnalysis: Segfault happened at: 0x7f0fa3229300 : movzbl 0xc0(%rdi),%eax PC (0x7f0fa3229300) ok source "0xc0(%rdi)" (0x00c0) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libunity StacktraceTop: g_desktop_app_info_get_is_hidden () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 gmenu_tree_load_sync () from /usr/lib/x86_64-linux-gnu/libgnome-menu-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/unity/unity-scope-applications.so Title: unity-scope-loader crashed with SIGSEGV in g_desktop_app_info_get_is_hidden() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1541084/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1541454] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid pointer: 0x00000000014b7180 ***
*** This bug is a duplicate of bug 1545268 *** https://bugs.launchpad.net/bugs/1545268 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545268, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1541454/+attachment/4563033/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1541454/+attachment/4563034/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1541454/+attachment/4563037/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1541454/+attachment/4563038/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1541454/+attachment/4563039/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1541454/+attachment/4563040/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1541454/+attachment/4563041/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1545268 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1541454 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid pointer: 0x014b7180 *** Status in libunity package in Ubuntu: New Bug description: 123 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': free(): invalid pointer: 0x014b7180 *** CrashCounter: 1 CurrentDesktop: Unity Date: Wed Feb 3 18:47:55 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2016-01-17 (16 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py -s files/gdrive.scope Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7fca58e52128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=, str=0x7fca58e4e27a "free(): invalid pointer", action=1) at malloc.c:4965 _int_free (av=, p=, have_lock=0) at malloc.c:3834 __GI___libc_free (mem=) at malloc.c:2950 g_hash_table_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': free(): invalid pointer: 0x014b7180 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1541454/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1546070] Re: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': malloc(): memory corruption: 0x0000000000f446d0 ***
*** This bug is a duplicate of bug 1545396 *** https://bugs.launchpad.net/bugs/1545396 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1545396, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1546070/+attachment/4572737/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1546070/+attachment/4572738/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1546070/+attachment/4572741/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1546070/+attachment/4572742/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1546070/+attachment/4572743/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1546070/+attachment/4572744/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1546070/+attachment/4572745/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1545396 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1546070 Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': malloc(): memory corruption: 0x00f446d0 *** Status in libunity package in Ubuntu: New Bug description: Please wait while we redirect you back to Yahoo ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity-scopes-runner 7.1.4+15.10.20151002-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-5.20-generic 4.4.1 Uname: Linux 4.4.0-5-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AssertionMessage: *** Error in `/usr/bin/python3': malloc(): memory corruption: 0x00f446d0 *** CrashCounter: 1 CurrentDesktop: Unity Date: Tue Feb 16 09:11:52 2016 Dependencies: ExecutablePath: /usr/share/unity-scopes/scope-runner-dbus.py InstallationDate: Installed on 2016-02-08 (7 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/unity-scopes/scope-runner-dbus.py /usr/share/unity-scopes/zotero/unity_zotero_daemon.py Signal: 6 SourcePackage: libunity StacktraceTop: __libc_message (do_abort=1, fmt=fmt@entry=0x385cd91128 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175 malloc_printerr (ptr=0xf446d0, str=0x385cd8d2fb "malloc(): memory corruption", action=) at malloc.c:4965 _int_malloc (av=av@entry=0x385cfc4c00 , bytes=bytes@entry=32) at malloc.c:3441 __GI___libc_malloc (bytes=32) at malloc.c:2895 ?? () Title: scope-runner-dbus.py assert failure: *** Error in `/usr/bin/python3': malloc(): memory corruption: 0x00f446d0 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1546070/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1548045] Re: notify-osd crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1275524 *** https://bugs.launchpad.net/bugs/1275524 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1275524, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1548045/+attachment/4577149/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1548045/+attachment/4577152/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1548045/+attachment/4577159/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1548045/+attachment/4577161/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1548045/+attachment/4577162/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1548045/+attachment/4577163/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1548045/+attachment/4577164/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1275524 notify-osd crashed with signal 5 in _XReply() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1548045 Title: notify-osd crashed with signal 5 in _XReply() Status in notify-osd package in Ubuntu: New Bug description: suposedly crashed but still appears to be running ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: notify-osd 0.9.35+16.04.20151201-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-7.22-generic 4.4.2 Uname: Linux 4.4.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 21 10:54:53 2016 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'GnomishDark' IconTheme: 'Alienware-Invader' InstallationDate: Installed on 2016-02-14 (6 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-7-generic root=UUID=38181c38-637a-4f92-9b7a-3da22ba14fd9 ro splash RelatedPackageVersions: xserver-xorg 1:7.7+13ubuntu1 libgl1-mesa-glx 11.1.2-1ubuntu1 libdrm2 2.4.67-1 xserver-xorg-video-intel 2:2.99.917+git20160218-1ubuntu1 xserver-xorg-video-ati 1:7.6.1-1 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev root sambashare sudo vboxusers wireshark dmi.bios.date: 03/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61MA-D2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61MA-D2V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1548045/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1275524] Re: notify-osd crashed with signal 5 in _XReply()
** Tags added: xenial -- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1275524 Title: notify-osd crashed with signal 5 in _XReply() Status in notify-osd package in Ubuntu: Confirmed Bug description: This occurred while I was away from the pc no other info. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: notify-osd 0.9.35+14.04.20140117.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Sun Feb 2 11:24:12 2014 DesktopSession: 'ubuntu' ExecutablePath: /usr/lib/x86_64-linux-gnu/notify-osd GtkTheme: 'Ambiance' IconTheme: 'buuf3.10' InstallationDate: Installed on 2014-01-08 (24 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108) MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529 ProcCmdline: /usr/lib/x86_64-linux-gnu/notify-osd ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libgl1-mesa-glx 10.1.0~git20140131.1d53603f-0ubuntu0sarvatt libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt xserver-xorg-video-intel 2:2.99.907+git20140131.f934ee78-0ubuntu0sarvatt xserver-xorg-video-ati 1:7.3.0-1ubuntu1 Signal: 5 SourcePackage: notify-osd StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetGeometry () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_window_get_geometry () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: notify-osd crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/11/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.8 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: G31M3-L V2(MS-7529) dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.8:bd03/11/2010:svnMICRO-STARINTERNATIONALCO.,LTD:pnMS-7529:pvr1.0:rvnMICRO-STARINTERNATIONALCO.,LTD:rnG31M3-LV2(MS-7529):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7529 dmi.product.version: 1.0 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1275524/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
