[Touch-packages] [Bug 1560722] Re: repositórios sumiram
** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1560722 Title: repositórios sumiram Status in glib2.0 package in Ubuntu: Incomplete Bug description: repositórios sumiram não sei o que fiz de errado. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-notification-daemon 1.12.1-1 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 22 19:41:03 2016 ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon InstallationDate: Installed on 2016-03-22 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon Signal: 5 SourcePackage: mate-notification-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so Title: mate-notification-daemon crashed with signal 5 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/glib2.0/+bug/1560722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected
Hi! I had the same problem with JBL TUNE500BT Headphones on Ubuntu 20.04. I did a kernel update to 5.8.9-050809-generic version using ubuntu- mainline-kernel.sh script [1]. I also uninstalled ofono and ofono- phonesim which I installed earlier when trying to fix this problem and reverted any changes I did to the default.pa file. It seems to be working now, but audio quality is awful when using HSP/HFP, which is related to another bug [2]. I don't know if it's a good solution, but maybe it will help someone. [1]: https://raw.githubusercontent.com/pimlie/ubuntu-mainline-kernel.sh/master/ubuntu-mainline-kernel.sh [2]: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1838151 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1576559 Title: Refused to switch profile to headset_head_unit: Not connected Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm trying to connect a bluetooth-speaker-with-microphone (Mi Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't use it as a headset with microphone. The device doesn't list in the "Input Devices" by default, and using the sound settings to change the profile of the device to HSP/HFP results in this log message: W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10. pulseaudio: Installed: 1:8.0-0ubuntu3 bluez: Installed: 5.37-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1576559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)
Same problem on Lenovo Ideapad 320-15IKB ** Changed in: alsa-driver (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1002978 Title: [meta-bug] Inverted Internal microphone (phase inversion) Status in alsa-driver package in Ubuntu: Confirmed Bug description: This is a metabug for all machines that are having phase inverted internal microphones. If your internal mic is either completely silent (no signal), or you can possibly pick a very small sound, with much background noise, even though you have set gain to maximum, there is something you could try. Install the pavucontrol application, start it and go to the "Input Devices" tab. Unlock the channels (there is a keylock icon), then mute the right channel while keeping the left channel at the volume you want. If the internal mic is now working correctly, you have an inverted internal mic, so that your right channel cancels out the left one. (If you're not running PulseAudio, you can try doing the same through AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try changing "Capture" level or "Internal Mic" or "Internal Mic Boost" using the Q,E,Z,C keys.) If so, please file a separate bug against the alsa-driver for your issue, make sure hardware info gets attached to it (either alsa-info as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones that follows when you do "ubuntu-bug alsa-driver" ), then write a comment in this bug, with your machine name and a pointer to the other bug. As time permits, I'll try to work on fixing them for the next Ubuntu release. Thanks! -- David Henningsson To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Sorry, completely forgot about it... :-/ So bug 1828639 is now fixed. I guess no need to fix gconf triggers now? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835376] Re: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned
*** This bug is a duplicate of bug 1828639 *** https://bugs.launchpad.net/bugs/1828639 ** This bug has been marked a duplicate of bug 1828639 Unlooping all the trigger loops! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1835376 Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned Status in gtk+2.0 package in Ubuntu: New Bug description: failed when i tried to do a partial upgrade because last upgrade already failed. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: libvlc-bin:amd64 3.0.6-1 ProcVersionSignature: Ubuntu 4.18.0-18.19-generic 4.18.20 Uname: Linux 4.18.0-18-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Thu Jul 4 10:16:45 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-04-06 (88 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: N/A SourcePackage: vlc Title: package libvlc-bin:amd64 3.0.6-1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1835376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1819079] Re: /usr/lib/gcr/gcr-prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** This bug has been marked a duplicate of bug 1627564 Crash due to assertion failure in ensure_surface_for_gicon [gtkiconhelper.c:493] (when png loader is missing/during upgrades) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1819079 Title: /usr/lib/gcr/gcr- prompter:6:g_assertion_message:g_assertion_message_error:ensure_surface_for_gicon:gtk_icon_helper_load_surface:gtk_icon_helper_ensure_surface Status in gcr package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gcr. This problem was most recently seen with package version 3.28.0-1, the problem page at https://errors.ubuntu.com/problem/b7be50bc0b853f28c864412a51e9f75d60558e7d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1819079/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
Fixed in 2.56 ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Fix Released Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
s/closed to/close to/ . -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Unknown Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default
Unfortunately you can't fix individual packages, and you're a bit wrong about Firefox. Yes it keeps running, but does not open new tabs/sub- processes until it's restarted, so effectively it's in a crippled state, which depending on your what you're working with through it, maybe constitute a Denial of Service. The simplest solution is not to change underlying software without user intervention, by default. An information system that modified its own code, unexpectedly without user intervention (which happens here as the user is not warned there's an update and asked if they want to proceed), is effectively a compromised system and that behavior is closed to malware. Please reconsider removing unattended-upgrades operating by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Won't Fix Status in unattended-upgrades package in Debian: Unknown Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Oh, nice. Maybe then gconf patches won't be needed. (Still need to fix FTBFS in Bionic, bug 1834211.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836328] [NEW] unattended-upgrades should not be enabled by default
Public bug reported: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1836328 Title: unattended-upgrades should not be enabled by default Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: The unattended-upgrades package and the whole concept of upgrading software automatically behind user's back is HARMFUL and the service/timer should NOT be enabled by default. It harms experience even for novice users with applications like Firefox preventing opening links until you restart it (which is terribad if you're in the middle of some work and don't want to do that at THAT particular moment!), and some other applications crashing in some cases, especially applications that run sub-processes interactively or on timers/cronjobs -- where updates to their libs or other dependencies create error states due to version/API/ABI mismatches. Please do not enable the service/timer by default and leave it to advanced users to enable assuming they understand the consequences. The same problem plagues snaps but that's a different bug report I suppose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
It could be that Debian won't need this change. Looks like all the triggers are now processed near the end of upgrade, due to changes in dpkg itself. Possibly related entry from dpkg 1.19.3 changelog: * dpkg: Introduce a new dependency try level for trigger processing. This completely defers trigger processing until after the dependency cycle breaking level, so to avoid generating artificial trigger cycles, when we end up trying to process triggers with yet unsatisifiable dependencies. Closes: #810724, #854478, #911620 https://bugs.debian.org/810724 And from dpkg 1.19.7 changelog: * dpkg: Split the trigger dependtry into two, the second of which will be the one checking trigger cycles when deferring trigger processing due to unsatisfiable dependencies. Closes: #928429 https://bugs.debian.org/928429 ** Bug watch added: Debian Bug tracker #810724 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810724 ** Bug watch added: Debian Bug tracker #928429 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928429 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
No, Debian package doesn't have this change. As for the bug reports, I only found a mention of this issue in a report for dpkg: https://bugs.debian.org/774794 ** Bug watch added: Debian Bug tracker #774794 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774794 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Description changed: - When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. + [Impact] + + During system upgrades, triggers for gconf2 might activate too early, + while some of its dependencies aren't configured yet. This happens + several times in a loop and stops the upgrade in the end. + + The attached debdiffs fix this issue by changing interest to interest- + noawait in debian/gconf2.triggers file. The triggers will now activate + near the end of upgrade. + + In addition, the debdiff for Bionic also contains a fix for FTBFS (bug + 1834211). + + [Test Case] + + Triggers for gconf2 are usually activated on changes in + /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with + GNOME) is most suitable for reproducing the issue. To reproduce it, + install that edition, apply all updates, then try upgrading to the next + release. + + [Regression Potential] + + None, interest-noawait trigger is known to work well in other packages + (comment 31). + + [Other Info] + + Even if Cosmic goes EOL next month, the fix for it might be worth it for + release upgrades. + + [Original Description] + + When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: - dpkg 1.18.4ubuntu1 - apt 1.2.3 + dpkg 1.18.4ubuntu1 + apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) ** Summary changed: - package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed + [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** Tags added: bionic cosmic disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: [SRU] package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: [Impact] During system upgrades, triggers for gconf2 might activate too early, while some of its dependencies aren't configured yet. This happens several times in a loop and stops the upgrade in the end. The attached debdiffs fix this issue by changing interest to interest- noawait in debian/gconf2.triggers file. The triggers will now activate near the end of upgrade. In addition, the debdiff for Bionic also contains a fix for FTBFS (bug 1834211). [Test Case] Triggers for gconf2 are usually activated on changes in /usr/share/GConf/gsettings folder, so the main Ubuntu edition (with GNOME) is most suitable for reproducing the issue. To reproduce it, install that edition, apply all updates, then try upgrading to the next release. [Regression Potential] None, interest-noawait trigger is known to work well in other packages (comment 31). [Other Info] Even if Cosmic goes EOL next month, the fix for it might be worth it for release upgrades. [Original Description] When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-pack
[Touch-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic
These fixes are also added to combined debdiff in bug 1551623. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 18.04 + build fix (bug 1834211) this can go into bionic-proposed in one diff ** Attachment added: "Debdiff with the fix for Bionic + build fix (bug 1834211)" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273780/+files/gconf-debdiff-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
For 18.04, a build fix is required first (bug 1834211). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 18.10 ** Attachment added: "Debdiff with the fix for Cosmic" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273779/+files/gconf-debdiff-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Fix for 19.04 ** Attachment added: "Debdiff with the fix for Disco" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+attachment/5273778/+files/gconf-debdiff-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
This is similar to what happened in the past with: - dbus (https://bugs.debian.org/771989) - cracklib-runtime (https://bugs.debian.org/854554) - shared-mime-info (https://bugs.debian.org/864953) It can be fixed the same way as those. I'll post the debdiffs with the fixes later. ** Bug watch added: Debian Bug tracker #771989 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771989 ** Bug watch added: Debian Bug tracker #854554 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854554 ** Bug watch added: Debian Bug tracker #864953 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864953 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733733] Re: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1733733 Title: portable apps crash while installing package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post- installation instalado retornou estado de saída de erro 128 Status in gconf package in Ubuntu: New Bug description: I installed orbital apps then it crashed, i changed to unity environment then tried to install again. I'm in need for portable apps for ubuntu. Description: Ubuntu 17.10 Release: 17.10 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: gconf2-common 3.2.6-4ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 Date: Tue Nov 21 21:44:08 2017 ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 128 InstallationDate: Installed on 2017-09-05 (77 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: gconf Title: package gconf2-common 3.2.6-4ubuntu1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 128 UpgradeStatus: Upgraded to artful on 2017-11-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1733733/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645384] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645384 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 Status in gconf package in Ubuntu: Confirmed Bug description: el problema se genero cuando intentaba descargar unos programas, no se completo la descarga y la tuve que reiniciar y posterior al reinicio aparecio el mensaje de error. ProblemType: Package DistroRelease: elementary 0.4 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Nov 28 09:10:05 2016 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 128 InstallationDate: Installed on 2016-11-26 (1 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645384/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698612] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698612 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett Status in gconf package in Ubuntu: New Bug description: this problem comes up after aech booting ProblemType: Package DistroRelease: elementary 0.4.1 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue May 23 18:21:04 2017 ErrorMessage: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett InstallationDate: Installed on 2017-05-22 (26 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: telepítve post-installation parancsfájl alfolyamat 128 hibakóddal kilépett UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698612/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1711472] Re: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie
*** This bug is a duplicate of bug 1509043 *** https://bugs.launchpad.net/bugs/1509043 ** This bug has been marked a duplicate of bug 1509043 package gconf2-common 3.2.6-3ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1711472 Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 Status in gconf package in Ubuntu: New Bug description: Hello, i want you say what this problem isn't today. I had this problem with ubuntu16.10 And today i have this problem with this new system based on ubuntu. I wish what you resolved this problem. Jo ProblemType: Package DistroRelease: elementary 0.4.1 Package: gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Aug 17 23:53:18 2017 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu6 [origin: Ubuntu] failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1711472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834211] Re: [SRU] gconf FTBFS in Bionic
** Attachment added: "Debdiff with the fix for Bionic" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+attachment/5273159/+files/gconf-debdiff-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834211] [NEW] [SRU] gconf FTBFS in Bionic
Public bug reported: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk-doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ftbfs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1834211 Title: [SRU] gconf FTBFS in Bionic Status in gconf package in Ubuntu: New Bug description: [Impact] Two issues make gconf FTBFS in Bionic: - outdated gtk-doc.make which fails with gtk-doc-tools >= 1.26 - missing dh-python in B-D The debdiff attached below fixes these issues and makes gconf build properly. [Test Case] Just install the needed build dependencies and try to build gconf. It will fail with an error from gtk-doc.make. Second issue: if gtk- doc.make is patched, the build will fail if dh-python isn't installed. [Regression Potential] None, you can't break it more than FTBFS :) [Other Info] Fixes are backported from Cosmic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1834211/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574029] Re: Upgrade failed
*** This bug is a duplicate of bug 1550292 *** https://bugs.launchpad.net/bugs/1550292 ** This bug has been marked a duplicate of bug 1550292 package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1574029 Title: Upgrade failed Status in shared-mime-info package in Ubuntu: New Bug description: At the end of the upgrade, a dialog box appeared "The upgrade has aborted. Your system could be in an unstable state. A recovery will run now (dpkg -configure - a). Nothing happened after closing the dialog box. After shutdown, boot up failed after grub tries to load something with this message "Starting up", then after 10 seconds this message "Gave up waiting for root device., common problems:.ALERT! UUID = 2476e..does not exist. The the boot process stopped at the initramfs prompt. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shared-mime-info 1.5-2 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 17:34:29 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-11-12 (162 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.5-2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1574029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615116] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1615116 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade Status in gconf package in Ubuntu: Confirmed Bug description: Error received when upgrading from 16.04 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Aug 19 18:49:10 2016 ErrorMessage: beroendeproblem - lämnar utlösare obehandlade InstallationDate: Installed on 2016-02-08 (193 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu2 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: beroendeproblem - lämnar utlösare obehandlade UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1615116/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1634151] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1634151 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld Status in gconf package in Ubuntu: New Bug description: Did an upgrade from Ubuntu 16.04 to 16.10, after rebooting the system the message occured ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Mon Oct 17 13:29:10 2016 ErrorMessage: vereistenproblemen - triggers blijven onbehandeld InstallationDate: Installed on 2016-05-04 (166 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: vereistenproblemen - triggers blijven onbehandeld UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1634151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1632415 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: error after updating from 16.04.1 to 16.10 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0 Uname: Linux 4.8.0-21-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 11 22:08:46 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-07-25 (78 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1632415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651222] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1651222 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: upgrade done with fail to install package gconf2 3.2.6ubuntu7 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Dec 19 13:13:09 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-19 (29 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-12-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1651222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645117] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1645117 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: -- ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic i686 ApportVersion: 2.20.3-0ubuntu8 Architecture: i386 Date: Sun Nov 27 21:29:34 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-09-03 (85 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-11-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1645117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636962] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1636962 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Wed Oct 26 23:42:05 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-27 (181 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2016-10-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1636962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701447] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1701447 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: The bugs being reported were generated automatically (without any of my input) when I allowed the system to upgrade itself from 16.04 to 16.10. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Thu Jun 29 21:58:13 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-11-27 (214 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-06-30 (0 days ago) mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 2017-01-03T13:15:58.771330 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1701447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698600] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698600 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: upgrading from 16.04 to 17.04 failed to install ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Sat Jun 17 18:19:27 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-09-13 (277 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-06-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1669632] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1669632 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-39.42-generic 4.8.17 Uname: Linux 4.8.0-39-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Thu Mar 2 20:56:22 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-04-10 (326 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1669632/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1656553] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1645117 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1656553 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: Error during partial update from 16.04 LTS to 16.10. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic i686 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: i386 Date: Sat Jan 14 15:46:26 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-12-14 (31 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1656553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698478] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1698478 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: would load but with errors ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Fri Jun 16 17:22:13 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2017-06-16 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2017-06-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1698478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681137] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug is no longer a duplicate of bug 1632415 package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1681137 Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: New Bug description: while upgrading from 16.04 to 16.10, it gave me this bug.. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Apr 9 01:01:29 2017 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-08-01 (250 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to yakkety on 2017-04-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1681137/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1741658] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 ***
https://bugs.launchpad.net/bugs/1551623
** This bug has been marked a duplicate of bug 1551623
package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems
- leaving triggers unprocessed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1741658
Title:
package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
Status in gconf package in Ubuntu:
New
Bug description:
System upgrage to Ubuntu 16.04 failed. During upgrade many packets were not
installed:
I wrote down the Dutch remarks "Kan gconf2 niet installeren" and many others.
Translated:
Failed to install during the systemupgrade:
==
gconf2 (+ "gconf2 will possibly not work")
gnupg-agent
gnupg2
libgdata22
gvfs-backends
adwaita-icon-theme-full
libgail-3-0
gstreamer1.0-plugins-bad
gstreamer0.10-plugins-good
gstreamer1.10-plugins-good
libgssdp-1.0-3
libupnp-1.0-4
libupnp-igd-1.0-4
libnice10
gstreamer1.0-nice
libfarstream-0.2-5
libpurple0
gnome-keyring
libgpgme11
libgmime-2.6-0
libwebkitgtk-3.0-0
geary
gnome-icon-theme
===
Hope the list is complete :-))
Since then only logging-out is possible, but the menu items: "Close the
system" ("Afsluiten" in Dutch) nor "Restart" gave any effect. Caption of this
menu is:
Lubuntu
Session Zorin-OS-lite 16.04
Best regards!
Dirk De Backer
mailto:debacker.d...@worldonline.be
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gconf2 3.2.6-3ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat Jan 6 15:32:06 2018
ErrorMessage: dependency problems - leaving triggers unprocessed
InstallationDate: Installed on 2015-12-19 (748 days ago)
InstallationMedia: Zorin 9 trusty - Release i386 (20140811)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.3
apt 1.2.24
SourcePackage: gconf
Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
problems - leaving triggers unprocessed
UpgradeStatus: Upgraded to xenial on 2018-01-06 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1741658/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610029] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1610029 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Confirmed Bug description: when upgrading from 14.04 LTS to 16.04 LTS this error came up during the upgrade ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Aug 3 23:57:59 2016 ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-08-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1610029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618364] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618364 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar Status in gconf package in Ubuntu: Confirmed Bug description: After upgrade from xenial to yakkety ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 09:34:31 2016 ErrorMessage: problemas com dependências - a deixar triggers por processar InstallationDate: Installed on 2016-02-15 (196 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160205) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemas com dependências - a deixar triggers por processar UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618492] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1618492 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati Status in gconf package in Ubuntu: Confirmed Bug description: crash ProblemType: Package DistroRelease: Ubuntu 16.10 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 30 14:35:15 2016 ErrorMessage: problemi con le dipendenze - trigger non elaborati InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3~rc2ubuntu3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: problemi con le dipendenze - trigger non elaborati UpgradeStatus: Upgraded to yakkety on 2016-08-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1618492/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573662] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1573662 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet Status in gconf package in Ubuntu: Confirmed Bug description: error occured during regular "do-release-upgrade". System remains in unstable condition. dpkg --configure -a / apt-get -f install continues the process (still running). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Fri Apr 22 17:05:44 2016 DuplicateSignature: package:gconf2:3.2.6-3ubuntu6:Abhängigkeitsprobleme - Trigger bleiben unverarbeitet ErrorMessage: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet InstallationDate: Installed on 2016-03-17 (35 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: Abhängigkeitsprobleme - Trigger bleiben unverarbeitet UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1573662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
*** This bug is a duplicate of bug 1551623 *** https://bugs.launchpad.net/bugs/1551623 ** This bug has been marked a duplicate of bug 1551623 package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1576539 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: bug happened while i'm upgrading ubuntu version from 15.10 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 29 08:16:36 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-03-05 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1576539/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812904] Re: [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco)
** Tags added: bionic cosmic eoan ** Summary changed: - [FTBFS] Doesn't compile with gtk-doc >=1.26 (Disco) + [FTBFS] Doesn't compile with gtk-doc >=1.26 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1812904 Title: [FTBFS] Doesn't compile with gtk-doc >=1.26 Status in hud package in Ubuntu: Confirmed Bug description: Gtkdoc-mktmpl was removed from gtk-doc 1.26. Instead use GtkDocConfig.cmake provided by gtk-doc-tools. See: https://github.com/GNOME/gtk- doc/commit/46df4354abed5724697fd5e39630c5bbc6637cc4#diff- 6023128f8e440b483f85968b0db7799e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1812904/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816024] [NEW] ubuntu-desktop should not hard depend on update-notifier (make it a recommended dep instead)
Public bug reported: The package `ubuntu-desktop` hard depends on `update-notifier` which is not good. It would be much better if it were a recommended dependency. Namely, the problem I initially wanted to report was with `update- notifier` not being configurable enough so it shows itself when you run apt manually on the command line. Pretty sure there's plenty of legitimate scenarios where desktops would be managed from command line. Think fleets of desktops in an office managed with SaltStack. Think scheduling updates to specific periods of time, outside of which you do not want to be nagged, even on single computers. And disabling updates from the Ubuntu Software app does not prevent the nagging when you operate `apt` manually. Neither does dconf-editor's com.ubuntu.update- notifier.no-show-notifications. Anyway, removing `update-notifier` solved the problem and then I realized that indeed, on machines where you do not want GUI for updates, you simply remove the package. And so this report is made. Please make it a recommended, not a hard dep of the desktop. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1816024 Title: ubuntu-desktop should not hard depend on update-notifier (make it a recommended dep instead) Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The package `ubuntu-desktop` hard depends on `update-notifier` which is not good. It would be much better if it were a recommended dependency. Namely, the problem I initially wanted to report was with `update- notifier` not being configurable enough so it shows itself when you run apt manually on the command line. Pretty sure there's plenty of legitimate scenarios where desktops would be managed from command line. Think fleets of desktops in an office managed with SaltStack. Think scheduling updates to specific periods of time, outside of which you do not want to be nagged, even on single computers. And disabling updates from the Ubuntu Software app does not prevent the nagging when you operate `apt` manually. Neither does dconf-editor's com.ubuntu .update-notifier.no-show-notifications. Anyway, removing `update-notifier` solved the problem and then I realized that indeed, on machines where you do not want GUI for updates, you simply remove the package. And so this report is made. Please make it a recommended, not a hard dep of the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1816024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816024] Re: ubuntu-desktop should not hard depend on update-notifier (make it a recommended dep instead)
See also bug #1210138. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1816024 Title: ubuntu-desktop should not hard depend on update-notifier (make it a recommended dep instead) Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The package `ubuntu-desktop` hard depends on `update-notifier` which is not good. It would be much better if it were a recommended dependency. Namely, the problem I initially wanted to report was with `update- notifier` not being configurable enough so it shows itself when you run apt manually on the command line. Pretty sure there's plenty of legitimate scenarios where desktops would be managed from command line. Think fleets of desktops in an office managed with SaltStack. Think scheduling updates to specific periods of time, outside of which you do not want to be nagged, even on single computers. And disabling updates from the Ubuntu Software app does not prevent the nagging when you operate `apt` manually. Neither does dconf-editor's com.ubuntu .update-notifier.no-show-notifications. Anyway, removing `update-notifier` solved the problem and then I realized that indeed, on machines where you do not want GUI for updates, you simply remove the package. And so this report is made. Please make it a recommended, not a hard dep of the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1816024/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787396] Re: ss crashes when using --no-header
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787396] Re: ss crashes when using --no-header
I've replicated the problem and the way I see it, all you need is --no- header and a filter with no matches. Filters with matches (found connections) won't cause a segfault. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound
Same: ASUS Prime x470-pro, Ryzen 7 2700X, 4.18.0 kernel. Cracking sound on the mic/line-in on ALC1220. The only thing, that somewhat helped, is increasing the default-fragment-size-msec to 75+ at /etc/pulse/daemon.conf. But it is a workaround, and it doesn't remove the cracking fully. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1716654 Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound Status in alsa-driver package in Ubuntu: Confirmed Bug description: Have checked under windows (same computer in dual-boot & same headset), and the sound is crystal clear, so 99% sure this is not a hardware problem. Motherboard is ASUS Crosshair Hero 6. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: paul 2587 F pulseaudio /dev/snd/controlC0: paul 2587 F pulseaudio /dev/snd/controlC1: paul 2587 F pulseaudio /dev/snd/controlC2: paul 2587 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Sep 12 11:48:05 2017 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic successful Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Pink Mic, Rear Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Generic successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago) dmi.bios.date: 07/28/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1501 dmi.board.asset.tag: Default string dmi.board.name: CROSSHAIR VI HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1716654/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
Solution per comment #3 fixed the problem for me as well, ureadahead is no longer spammy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
92454 entries here, Ubuntu 18.04, fresh installation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765230] Re: Immediate logout when using Chrome (and not only it)
The bug was in the Amdgpu-pro drivers. Uninstalled them, and the problem disappeared. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765230] Re: Immediate logout when using Chrome (and not only it)
Here are the main syslog lines when it happens: Apr 19 22:52:00 vladiat0r dbus-daemon[929]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.97' (uid=1000 pid=2112 comm="/opt/google/chrome/chrome " label="unconfined") Apr 19 22:52:00 vladiat0r systemd[1]: Starting Hostname Service... Apr 19 22:52:00 vladiat0r org.a11y.Bus[1158]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Apr 19 22:52:00 vladiat0r org.a11y.Bus[1158]: after 6865 requests (6865 known processed) with 0 events remaining. Apr 19 22:52:00 vladiat0r org.kde.kuiserver[1158]: kuiserver: Fatal IO error: client killed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1765230] [NEW] Immediate logout when using Chrome (and not only it)
Public bug reported: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3806 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3806:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu performance ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765230 Title: Immediate logout when using Chrome (and not only it) Status in xorg package in Ubuntu: New Bug description: Sometimes when I open a new tab or start downloading a file with the Chrome browser, the system logs me out. Then this problem persists so that I'm logged out very fast, and only reboot helps. Starting Firefox after the first crash also leads to logout. What exact information can I provide (some logs etc)? Thank you. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Thu Apr 19 01:56:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: amdgpu, 17.40-492261: added virtualbox, 5.2.8, 4.15.0-13-generic, x86_64: installed virtualbox, 5.2.8, 4.15.0-15-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev e7) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/580] [1462:3418] InstallationDate: Installed on 2018-04-11 (7 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed root=UUID=7dbb3ef1-f889-4f8b-8243-ddccfd6bc4c2 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatu
[Touch-packages] [Bug 1762807] Re: gnome-session-bin installed on Ubuntu MATE
Thanks, today's ISO doesn't contain gnome-session-bin anymore. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1762807 Title: gnome-session-bin installed on Ubuntu MATE Status in software-properties package in Ubuntu: Fix Released Bug description: Ubuntu MATE seeds software-properties-gtk which causes gnome-session- bin to be pulled into the Ubuntu MATE image. This issue arises because debian/control doesn't Recommends: mate-session-manager for software- properties-gtk. To resolve this issue debian/control for software-properties-gtk should be updated to: Recommends: gnome-session-bin | xfce4-session | lubuntu-default- settings | lxqt-session | mate-session-manager, gnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1762807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613363] Re: /usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date
** Package changed: engrampa (Ubuntu) => gtk+2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1613363 Title: /usr/bin/engrampa:11:g_type_check_instance_is_fundamentally_a:g_object_get_qdata:detach_from_style:clear_cache:ensure_cache_up_to_date Status in gtk+2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding engrampa. This problem was most recently seen with version 1.12.0-2, the problem page at https://errors.ubuntu.com/problem/2f8bf782a90fe3ab90595f0ab71cdafa82f08b7f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1613363/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569068] Re: /usr/bin/mate-settings-daemon:ERROR:pulse/glib-mainloop.c:407:glib_defer_free: assertion failed: (!e->dead)
** Package changed: mate-settings-daemon (Ubuntu) => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1569068 Title: /usr/bin/mate-settings-daemon:ERROR:pulse/glib- mainloop.c:407:glib_defer_free: assertion failed: (!e->dead) Status in pulseaudio package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/1b3afc018f02173501b79b75651ec747d69300b7 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1569068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1664775] Re: /usr/bin/mate-settings-daemon:11:malloc_consolidate:_int_malloc:__libc_calloc:_snd_ctl_pulse_open:snd_ctl_open_conf
** Package changed: mate-settings-daemon (Ubuntu) => alsa-lib (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1664775 Title: /usr/bin/mate-settings- daemon:11:malloc_consolidate:_int_malloc:__libc_calloc:_snd_ctl_pulse_open:snd_ctl_open_conf Status in alsa-lib package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with package version 1.14.0-1~xenial1.01, the problem page at https://errors.ubuntu.com/problem/669d26d753efa0be401d9fbc9242e66634d3d763 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1664775/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440349] Re: imaens não abrem
*** This bug is a duplicate of bug 555238 *** https://bugs.launchpad.net/bugs/555238 ** Changed in: ubuntu-mate Status: Expired => Invalid ** Package changed: caja (Ubuntu) => jasper (Ubuntu) ** This bug has been marked a duplicate of bug 555238 crash on .jp2 files in jpc_qmfb_join_colgrp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/1440349 Title: imaens não abrem Status in ubuntu-mate: Invalid Status in jasper package in Ubuntu: Expired Bug description: MEUS ARQUIVOS A PASTA ABRE E FECHA QUANDO EU ESCOLHO UM ARQUIVO DE IMAGENS ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: caja 1.8.2-3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 ApportVersion: 2.17-0ubuntu1 Architecture: i386 CrashCounter: 1 CurrentDesktop: MATE Date: Sat Apr 4 11:19:46 2015 ExecutablePath: /usr/bin/caja InstallationDate: Installed on 2015-04-03 (1 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta i386 (20150326) ProcCmdline: caja ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: caja 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-mate/+bug/1440349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 555238] Re: crash on .jp2 files in jpc_qmfb_join_colgrp
** Summary changed: - nautilus crashed with SIGSEGV in jpc_qmfb_join_colgrp() + crash on .jp2 files in jpc_qmfb_join_colgrp -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jasper in Ubuntu. https://bugs.launchpad.net/bugs/555238 Title: crash on .jp2 files in jpc_qmfb_join_colgrp Status in jasper package in Ubuntu: Confirmed Bug description: Binary package hint: nautilus ProblemType: Crash DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.0-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Sun Apr 4 13:29:52 2010 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcCmdline: nautilus ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f23eb32ae1c : mov %r8,(%r10,%rax,1) PC (0x7f23eb32ae1c) ok source "%r8" ok destination "(%r10,%rax,1)" (0x7f23fabee970) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: jpc_qmfb_join_colgrp () from /usr/lib/libjasper.so.1 jpc_ns_synthesize () from /usr/lib/libjasper.so.1 jpc_tsfb_synthesize2 () from /usr/lib/libjasper.so.1 jpc_tsfb_synthesize () from /usr/lib/libjasper.so.1 ?? () from /usr/lib/libjasper.so.1 Title: nautilus crashed with SIGSEGV in jpc_qmfb_join_colgrp() UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jasper/+bug/555238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670898] Re: crash after spi_cache_foreach from impl_GetItems
** Summary changed: - /usr/bin/mate-settings-daemon:11:g_type_check_instance_is_fundamentally_a:g_object_ref:g_hash_table_foreach:spi_cache_foreach:impl_GetItems + crash after spi_cache_foreach from impl_GetItems ** Package changed: mate-settings-daemon (Ubuntu) => at-spi2-atk (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1670898 Title: crash after spi_cache_foreach from impl_GetItems Status in at-spi2-atk package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with package version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/f507ea21d5337991672738917ae190e6e86f76e2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1670898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style
** Summary changed: - mate-panel crashed with SIGSEGV in g_slist_remove_all() + crash in g_slist_remove_all from gtk_rc_clear_realized_style -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1555331 Title: crash in g_slist_remove_all from gtk_rc_clear_realized_style Status in gtk+2.0 package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Won't Fix Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 9 22:49:55 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-02-25 (12 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x7f4fa6439b1c :cmp %rbp,(%rdi) PC (0x7f4fa6439b1c) ok source "%rbp" ok destination "(%rdi)" (0x160016) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_slist_remove_all() 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/gtk+2.0/+bug/1555331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617552] Re: mate-notification-daemon crashed with SIGABRT in __assert_fail_base()
*** This bug is a duplicate of bug 1598142 *** https://bugs.launchpad.net/bugs/1598142 ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1598142 mate-notification-daemon assert failure: mate-notification-daemon: ../../../../src/cairo.c:305: cairo_destroy: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed. ** This bug is no longer a duplicate of bug 1598142 mate-notification-daemon assert failure: mate-notification-daemon: ../../../../src/cairo.c:305: cairo_destroy: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed. ** Package changed: ubuntu => mate-notification-daemon (Ubuntu) ** This bug has been marked a duplicate of bug 1598142 mate-notification-daemon assert failure: mate-notification-daemon: ../../../../src/cairo.c:305: cairo_destroy: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1617552 Title: mate-notification-daemon crashed with SIGABRT in __assert_fail_base() Status in mate-notification-daemon package in Ubuntu: New Bug description: Just popped out of nowhere. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mate-notification-daemon 1.14.1-1build1 ProcVersionSignature: Ubuntu 4.4.0-9134.53-powerpc64-smp 4.4.15 Uname: Linux 4.4.0-9134-powerpc64-smp ppc64 ApportVersion: 2.20.3-0ubuntu7 Architecture: powerpc CurrentDesktop: MATE Date: Sat Aug 27 13:10:34 2016 ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon InstallationDate: Installed on 2016-03-26 (153 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc (20160326) ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=de_AT:de LANG=de_AT.UTF-8 Signal: 6 SourcePackage: mate-notification-daemon StacktraceTop: raise () from /lib/powerpc-linux-gnu/libc.so.6 abort () from /lib/powerpc-linux-gnu/libc.so.6 ?? () from /lib/powerpc-linux-gnu/libc.so.6 __assert_fail () from /lib/powerpc-linux-gnu/libc.so.6 cairo_destroy () from /usr/lib/powerpc-linux-gnu/libcairo.so.2 Title: mate-notification-daemon crashed with SIGABRT in raise() 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/mate-notification-daemon/+bug/1617552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580686] Re: scp-dbus-service.py crashed with signal 5 in _XReply()
** Package changed: system-config-printer (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - scp-dbus-service.py crashed with signal 5 in _XReply() + crash in XTranslateCoordinates from gdk_window_x11_get_root_coords -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1580686 Title: crash in XTranslateCoordinates from gdk_window_x11_get_root_coords Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Printed 3 copys of one document with setting 2 pages on 1 sheet. Job printed normally but crash report appeared afterwards. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CupsErrorLog: E [11/May/2016:18:27:44 +0200] [cups-deviced] PID 13760 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Wed May 11 18:32:16 2016 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2016-04-30 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.5 Lpstat: device for FS-1010: usb://Kyocera/FS-1010?serial=XAL4584303 MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 PpdFiles: FS-1010: Kyocera Mita FS-1010 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash vt.handoff=7 Signal: 5 SourcePackage: system-config-printer StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gtk_tooltip_trigger_tooltip_query () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: scp-dbus-service.py crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare sudo video dmi.bios.date: 03/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B150-HD3P-CF 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: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.: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/gtk+3.0/+bug/1580686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725150] Re: apport-gtk crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from ensure_surface_for_gicon() from gtk_icon_helper_load_surface() from gtk
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** This bug has been marked a duplicate of bug 1627564 crash due to assertion in ensure_surface_for_gicon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1725150 Title: apport-gtk crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from ensure_surface_for_gicon() from gtk_icon_helper_load_surface() from gtk_icon_helper_ensure_surface() Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.7-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/89ba75aaa8b360ea7a348d4f4f7d24875f1f6180 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1725150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1599401] Re: crash in XTranslateCoordinates from gdk_x11_display_translate_event
** Summary changed: - mate-settings-daemon crashed with signal 5 in _XReply() + crash in XTranslateCoordinates from gdk_x11_display_translate_event -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1599401 Title: crash in XTranslateCoordinates from gdk_x11_display_translate_event Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: polihron@polihron-K56CA:~$ lsb_release -rd Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mate-settings-daemon 1.14.0-1 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jul 6 10:50:49 2016 ExecutablePath: /usr/bin/mate-settings-daemon InstallationDate: Installed on 2016-07-01 (4 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160629.1) ProcCmdline: /usr/bin/mate-settings-daemon Signal: 5 SourcePackage: mate-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: mate-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1599401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1594609] Re: /usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func
** Package changed: mate-panel (Ubuntu) => gtk+2.0 (Ubuntu) ** Summary changed: - /usr/bin/mate-panel:6:g_assertion_message:g_assertion_message_expr:get_icon_fallback:gtk_recent_chooser_menu_create_item:idle_populate_func + crash due to assertion in get_icon_fallback from gtk_recent_chooser_menu_create_item -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1594609 Title: crash due to assertion in get_icon_fallback from gtk_recent_chooser_menu_create_item Status in gtk+2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-panel. This problem was most recently seen with version 1.12.2-1, the problem page at https://errors.ubuntu.com/problem/96ae198a578de2353a3cc778896a83a10ab7d131 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1594609/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1627564] Re: was doing an upgrade and this created a trouble report
** Package changed: lightdm-gtk-greeter (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - was doing an upgrade and this created a trouble report + crash due to assertion in ensure_surface_for_gicon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1627564 Title: crash due to assertion in ensure_surface_for_gicon Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: bubble opened up indicating there was a failure during the latest update. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: lightdm-gtk-greeter 2.0.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-16.17-generic 4.8.0-rc7 Uname: Linux 4.4.0-9136-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 Date: Sun Sep 25 20:37:06 2016 ExecutablePath: /usr/sbin/lightdm-gtk-greeter InstallationDate: Installed on 2016-08-04 (52 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Alpha i386 (20160727) ProcCmdline: /usr/sbin/lightdm-gtk-greeter ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: lightdm-gtk-greeter UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: modified.conffile..etc.lightdm.lightdm-gtk-greeter.conf: [greeter] theme-name = Lubuntu-dark-panel mtime.conffile..etc.lightdm.lightdm-gtk-greeter.conf: 2016-08-14T22:33:57.293011 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1627564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1678693] Re: mate-notification-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** Package changed: mate-notification-daemon (Ubuntu) => gtk+3.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1627564 crash due to assertion in ensure_surface_for_gicon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1678693 Title: mate-notification-daemon crashed with SIGABRT in g_assertion_message() Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: occurred while installing packages ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-notification-daemon 1.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-13.15-generic 4.10.1 Uname: Linux 4.10.0-13-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Apr 2 23:04:26 2017 ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon InstallationDate: Installed on 2017-04-01 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1) ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_US LANG=en_US.UTF-8 Signal: 6 SourcePackage: mate-notification-daemon StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.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 Title: mate-notification-daemon crashed with SIGABRT in g_assertion_message() 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/gtk+3.0/+bug/1678693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1201854] Re: gnome-settings-daemon crashed with signal 5 in _XReply()
** Package changed: gnome-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - gnome-settings-daemon crashed with signal 5 in _XReply() + crash in XGetWindowProperty from read_settings from gdk_xsettings_manager_window_filter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1201854 Title: crash in XGetWindowProperty from read_settings from gdk_xsettings_manager_window_filter Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: This happened immediately after a reboot for updates. Immediately after I checked for more updates and there were some, meaning this bug might already be fixed. About the updates, I noticed that a few 'failed to download' but running sudo apt-get upgrade they installed fine. I don't know if this is related but it might be. This has probably happened several times, but I don't think it's a regular pattern. Running 13.10 Alpha. Otherwise seems to be pretty stable so far despite the minor bugs. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.6.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Fri Jul 12 23:43:27 2013 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1372327096 InstallationDate: Installed on 2013-06-14 (28 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /home/karatekid ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gnome-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to saucy on 2013-07-12 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1201854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751948] Re: /usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event
*** This bug is a duplicate of bug 1201854 *** https://bugs.launchpad.net/bugs/1201854 ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1201854 crash in XGetWindowProperty from read_settings from gdk_xsettings_manager_window_filter -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1751948 Title: /usr/bin/nautilus:5:XGetWindowProperty:read_settings:gdk_xsettings_manager_window_filter:gdk_event_apply_filters:gdk_event_source_translate_event Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.18.5-0ubuntu1~xenial1, the problem page at https://errors.ubuntu.com/problem/190c0ee1caee53020969ace002fde3c337a9d748 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1751948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670463] Re: crash in XGetWindowProperty from gdk_check_wm_desktop_changed
** Summary changed: - mate-settings-daemon crashed with signal 5 in _XReply() + crash in XGetWindowProperty from gdk_check_wm_desktop_changed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1670463 Title: crash in XGetWindowProperty from gdk_check_wm_desktop_changed Status in gtk+3.0 package in Ubuntu: New Bug description: start up error ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-settings-daemon 1.17.1-0~ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Mon Mar 6 20:29:40 2017 ExecutablePath: /usr/bin/mate-settings-daemon InstallationDate: Installed on 2016-09-09 (177 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/bin/mate-settings-daemon Signal: 5 SourcePackage: mate-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: mate-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to zesty on 2016-10-16 (140 days ago) UserGroups: adm audio cdrom dialout dip lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1670463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427332] Re: nautilus crashed with signal 5 in _XReply()
** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - nautilus crashed with signal 5 in _XReply() + crash in XGetWindowProperty from gdk_check_wm_state_changed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1427332 Title: crash in XGetWindowProperty from gdk_check_wm_state_changed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: none ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Mon Mar 2 16:17:00 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-10-24 (129 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcCmdline: nautilus ProcEnviron: LANGUAGE=es_UY:es PATH=(custom, no user) LANG=es_UY.UTF-8 SHELL=/bin/bash TERM=unknown Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: nautilus crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to vivid on 2015-01-05 (56 days ago) UserGroups: usr_lib_nautilus: brasero3.12.0-0ubuntu2 evince 3.14.1-0ubuntu5 file-roller3.14.2-0ubuntu4 gnome-terminal 3.14.2-0ubuntu2 nautilus-share 0.7.3-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1427332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1744744] Re: /usr/bin/mate-settings-daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_tr
*** This bug is a duplicate of bug 1427332 *** https://bugs.launchpad.net/bugs/1427332 ** Package changed: mate-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1427332 crash in XGetWindowProperty from gdk_check_wm_state_changed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1744744 Title: /usr/bin/mate-settings- daemon:5:XGetWindowProperty:gdk_check_wm_state_changed:gdk_x11_display_translate_event:_gdk_x11_event_translator_translate:gdk_event_source_translate_event Status in gtk+3.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with package version 1.18.2-1, the problem page at https://errors.ubuntu.com/problem/ce324a21097bbf499a8ddc2db96e9a01d4252f07 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1744744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359308] Re: crash due to assertion in gail_focus_notify_when_idle: code should not be reached
** Summary changed: - mate-panel crashed when using window list + crash due to assertion in gail_focus_notify_when_idle: code should not be reached -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1359308 Title: crash due to assertion in gail_focus_notify_when_idle: code should not be reached Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: On an Ubuntu MATE utopic amd64 system, mate-panel 1.8.0+dfsg1-2 crashed when I clicked on an item in the window list (located in the bottom panel). The panel reappeared and continued working correctly. This happened while apt-get was upgrading packages, but mate-panel was not one of the packages being upgraded. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-panel 1.8.0+dfsg1-2 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Wed Aug 20 13:21:43 2014 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2014-08-19 (1 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) ProcCmdline: mate-panel ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: mate-panel 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/gtk+2.0/+bug/1359308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1635812] Re: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace()
** Tags removed: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1635812 Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() Status in poppler package in Ubuntu: Fix Released Bug description: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: atril 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Sat Oct 22 09:43:08 2016 ExecutablePath: /usr/bin/atril-thumbnailer InstallationDate: Installed on 2016-05-14 (160 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: atril-thumbnailer -s 128 file:///home/username/Documents/jedi_complaint.pdf /tmp/.mate_desktop_thumbnail.8JDPPY SegvAnalysis: Segfault happened at: 0x7fdcb0258990 : mov 0x50(%rdi),%eax PC (0x7fdcb0258990) ok source "0x50(%rdi)" (0x0050) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: atril StacktraceTop: cmsGetColorSpace () from /usr/lib/x86_64-linux-gnu/liblcms2.so.2 GfxICCBasedColorSpace::parse(Array*, OutputDev*, GfxState*, int) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 GfxColorSpace::parse(GfxResources*, Object*, OutputDev*, GfxState*, int) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 Page::loadThumb(unsigned char**, int*, int*, int*) () from /usr/lib/x86_64-linux-gnu/libpoppler.so.58 poppler_page_get_thumbnail () from /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8 Title: atril-thumbnailer crashed with SIGSEGV in cmsGetColorSpace() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1635812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
*** This bug is a duplicate of bug 1438014 *** https://bugs.launchpad.net/bugs/1438014 Forgot to mention that 016_no_offscreen_widgets_grabbing.patch had never been accepted upstream, as I learned in the discussion at https://bugzilla.gnome.org/607668. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Invalid Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() 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/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438014] Re: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a()
** Package changed: gnome-terminal (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() + gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts ** Tags removed: vivid ** Tags added: bionic xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1438014 Title: gnome-terminal-server and mate-terminal crash when setting keyboard shortcuts Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: I put my laptop to sleep for an hour or so; when I restored it, gnome- terminal had crashed. It did not do this the previous time I suspended my laptop today, so I doubt that's immediately related. This crash can be reproduced by setting a shortcut in preferences. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: gnome-terminal 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 30 00:19:43 2015 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2014-02-03 (419 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/lib/gnome-terminal/gnome-terminal-server ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_US PATH=(custom, user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f98e2afbf1f : testb $0x4,0x16(%rax) PC (0x7f98e2afbf1f) ok source "$0x4" ok destination "0x16(%rax)" (0xbcae) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: gnome-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel (widget=0x2580c30) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwidget.c:11382 window_group_cleanup_grabs (group=, window=window@entry=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:110 gtk_window_group_add_window (window_group=0x27e5c40, window=0x252a230) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindowgroup.c:169 gtk_window_set_transient_for (window=0x252a230, parent=0x23ac7d0) at /build/buildd/gtk+3.0-3.14.9/./gtk/gtkwindow.c:3134 Title: gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() UpgradeStatus: Upgraded to vivid on 2015-03-29 (0 days ago) UserGroups: adm cdrom dialout dip kvm libvirtd lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1438014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
*** This bug is a duplicate of bug 1438014 *** https://bugs.launchpad.net/bugs/1438014 Surprise, it's been affecting gnome-terminal for years: bug 1438014. ** This bug has been marked a duplicate of bug 1438014 gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Invalid Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() 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/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Changed in: mate-terminal (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Invalid Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() 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/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() 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/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1680436] Re: notification-area-applet crashed with signal 5 in _XReply()
*** This bug is a duplicate of bug 1599401 *** https://bugs.launchpad.net/bugs/1599401 ** Package changed: mate-panel (Ubuntu) => gtk+3.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1599401 mate-settings-daemon crashed with signal 5 in _XReply() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1680436 Title: notification-area-applet crashed with signal 5 in _XReply() Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Crash ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-panel 1.18.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-15.17-generic 4.10.5 Uname: Linux 4.10.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Thu Apr 6 12:58:12 2017 ExecutablePath: /usr/lib/mate-panel/notification-area-applet InstallationDate: Installed on 2017-04-06 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Beta amd64 (20170321.1) ProcCmdline: /usr/lib/mate-panel/notification-area-applet ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=pt:pt_BR:en LANG=pt_PT.UTF-8 Signal: 5 SourcePackage: mate-panel StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: notification-area-applet crashed with signal 5 in _XReply() 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/gtk+3.0/+bug/1680436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1233760] Re: Sure way to crash Gnome-Shell in Ubuntu 13.10 and Ubuntu Gnome 13.10
** No longer affects: dconf (Fedora) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1233760 Title: Sure way to crash Gnome-Shell in Ubuntu 13.10 and Ubuntu Gnome 13.10 Status in d-conf package in Ubuntu: Confirmed Bug description: This affects Gnome-Shell 3.8 up to the latest build from Gnome3-Staging Gnome-Shell 3.10 on Ubuntu 13.10 and Ubuntu Gnome 13.10 daily builds, as of today! 1. Start gnome-terminal (has to be gnome-terminal - other term apps don't appear to produce this bug). 2. run sudo su and enter your password 3. run gedit or nautilus but definitely gedit is confirmed by 1 other person 4. Flick your mouse up to Activities 5. Gnome-Shell is dead ctrl+alt+f1 - login and run stop gdm or stop lightdm depending on your Ubuntu build start lightdm or gdm - attempt to login to gnome - no desktop will appear and if you switch back to the console you can see gnome-shell running like crazy. I've tried killing X, and confirmed all gnome service aren't running then tried start gdm or start lightdm and still nothing works. Have to restart PC to recover. Happy to test this and give you any logs you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1233760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379628] Re: gedit crashed with signal 5 in _XReply()
** Package changed: gedit (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1379628 Title: gedit crashed with signal 5 in _XReply() Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Don't recall exactly what happened, but gedit crashed while I was typing up a document. :( ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: gedit 3.10.4-0ubuntu6 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Oct 9 18:54:33 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2014-09-26 (13 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) ProcCmdline: gedit ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XIGetClientPointer () from /usr/lib/x86_64-linux-gnu/libXi.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: gedit crashed with signal 5 in _XReply() 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/gtk+3.0/+bug/1379628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713360] Re: mate-settings-daemon crashed with signal 5
** This bug is no longer a duplicate of bug 1621074 mate-settings-daemon crashed with signal 5 in _XReply() ** Package changed: mate-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1713360 Title: mate-settings-daemon crashed with signal 5 Status in gtk+3.0 package in Ubuntu: New Bug description: Nothing to added. Apport just popped up to report this. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: mate-settings-daemon 1.18.1-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Sun Aug 27 20:11:44 2017 ExecutablePath: /usr/bin/mate-settings-daemon InstallationDate: Installed on 2017-06-16 (72 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170606) ProcCmdline: /usr/bin/mate-settings-daemon ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/fish Signal: 5 SourcePackage: mate-settings-daemon StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libX11.so.6 () at /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () at /usr/lib/x86_64-linux-gnu/libX11.so.6 XIGetClientPointer () at /usr/lib/x86_64-linux-gnu/libXi.so.6 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: mate-settings-daemon crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1713360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670463] Re: mate-settings-daemon crashed with signal 5 in _XReply()
** This bug is no longer a duplicate of bug 1621074 mate-settings-daemon crashed with signal 5 in _XReply() ** Package changed: mate-settings-daemon (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1670463 Title: mate-settings-daemon crashed with signal 5 in _XReply() Status in gtk+3.0 package in Ubuntu: New Bug description: start up error ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-settings-daemon 1.17.1-0~ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: MATE Date: Mon Mar 6 20:29:40 2017 ExecutablePath: /usr/bin/mate-settings-daemon InstallationDate: Installed on 2016-09-09 (177 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/bin/mate-settings-daemon Signal: 5 SourcePackage: mate-settings-daemon StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XGetWindowProperty () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: mate-settings-daemon crashed with signal 5 in _XReply() UpgradeStatus: Upgraded to zesty on 2016-10-16 (140 days ago) UserGroups: adm audio cdrom dialout dip lpadmin netdev plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1670463/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667227] Re: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1667227 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() - while editing Keyboard Shortcuts Status in gnome-terminal package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Bug description: 1) $ lsb_release -rd Description: Ubuntu Zesty Zapus (development branch) Release: 17.04 Installed as Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 2) $ apt-cache policy mate-terminal mate-terminal: Installed: 1.17.0-0ubuntu1 Candidate: 1.17.0-0ubuntu1 3) Open mate-terminal Select "Edit" -> "Keyboard Shortcuts" Select "Help"->"Contents", click on default shortcut key "F1" to change Try to set it to various key sequences. Sometimes bug is triggered by pressing "Fn" key with some of Alt/Ctrl/Shift, sometimes by selecting Ctrl-Shift-W / Crtl-Shift-Alt-W Expected: changed keyboard shortcut for "Help"->"Contents" 4) Abort and closed mate-terminal ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: mate-terminal 1.17.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8 Uname: Linux 4.10.0-8-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 23 09:33:19 2017 ExecutablePath: /usr/bin/mate-terminal ExecutableTimestamp: 1484233434 InstallationDate: Installed on 2017-02-22 (1 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) ProcCmdline: mate-terminal ProcCwd: /home/user SegvAnalysis: Segfault happened at: 0x7f883e41c321 : testb $0x4,0x16(%rax) PC (0x7f883e41c321) ok source "$0x4" ok destination "0x16(%rax)" (0x7001e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-terminal StacktraceTop: g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 gtk_widget_get_toplevel () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_group_add_window () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_set_transient_for () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: mate-terminal crashed with SIGSEGV in g_type_check_instance_is_a() 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/gnome-terminal/+bug/1667227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US
Testing in Xubuntu 14.04... - have ru_RU locale - apt-get source gdebi (0.9.5.3ubuntu3 from trusty-proposed) - cd gdebi-0.9.5.3ubuntu3 - debuild -us -uc - build successful, no more FTBFS ** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: Fix Released Status in gdebi source package in Trusty: Fix Committed Status in gdebi package in Debian: Fix Released Bug description: [Impact] It's impossible to build gdebi from source with the locale other than en_US in Trusty. It had been fixed in gdebi 0.9.5.5, which is available in newer releases, starting from Vivid. The backported fix can be applied in Trusty. The debdiff which is attached to this report contains the fix. [Test Case] Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first log attached to this report. [Regression Potential] The patch only affects a test which is launched during the build, it doesn't affect runtime at all. The test is passed successfully with the patch. All the tests are independent from each other, so the patch can't introduce any regressions to other tests. [Original Description] System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US
** Attachment added: "Debdiff with the fix for Trusty, edited" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+attachment/4948954/+files/gdebi-debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: Fix Released Status in gdebi source package in Trusty: Triaged Status in gdebi package in Debian: Fix Released Bug description: [Impact] It's impossible to build gdebi from source with the locale other than en_US in Trusty. It had been fixed in gdebi 0.9.5.5, which is available in newer releases, starting from Vivid. The backported fix can be applied in Trusty. The debdiff which is attached to this report contains the fix. [Test Case] Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first log attached to this report. [Regression Potential] The patch only affects a test which is launched during the build, it doesn't affect runtime at all. The test is passed successfully with the patch. All the tests are independent from each other, so the patch can't introduce any regressions to other tests. [Original Description] System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US
** Patch removed: "Debdiff with the fix for Trusty" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+attachment/4947390/+files/gdebi-debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: Fix Released Status in gdebi source package in Trusty: Triaged Status in gdebi package in Debian: Fix Released Bug description: [Impact] It's impossible to build gdebi from source with the locale other than en_US in Trusty. It had been fixed in gdebi 0.9.5.5, which is available in newer releases, starting from Vivid. The backported fix can be applied in Trusty. The debdiff which is attached to this report contains the fix. [Test Case] Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first log attached to this report. [Regression Potential] The patch only affects a test which is launched during the build, it doesn't affect runtime at all. The test is passed successfully with the patch. All the tests are independent from each other, so the patch can't introduce any regressions to other tests. [Original Description] System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US
[Impact] It's impossible to build gdebi from source with the locale other than en_US in Trusty. It had been fixed in gdebi 0.9.5.5, which is available in newer releases, starting from Vivid. The backported fix can be applied in Trusty. The debdiff which is attached to this report contains the fix. [Test Case] Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first log attached to this report. [Regression Potential] The patch only affects a test which is launched during the build, it doesn't affect runtime at all. The test is passed successfully with the patch. All the tests are independent from each other, so the patch can't introduce any regressions to other tests. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: New Status in gdebi package in Debian: Fix Released Bug description: System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633766] Re: Unescaped left brace in regex is deprecated
** Project changed: linuxmint => debconf (Ubuntu)
** Changed in: debconf (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1633766
Title:
Unescaped left brace in regex is deprecated
Status in debconf package in Ubuntu:
Fix Released
Bug description:
uname -a
Linux keswork 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC 2014
x86_64 x86_64 x86_64 GNU/Linux
Linux Mint 17.3
I am upgrading to 18.0
Preparing to unpack .../xserver-xorg_1%3a7.7+13ubuntu3_amd64.deb ...
Unescaped left brace in regex is deprecated, passed through in regex; marked
by <-- HERE in m/^(.*?)(\\)?\${ <-- HERE ([^{}]+)}(.*)$/ at
/usr/share/perl5/Debconf/Question.pm line 72.
Unescaped left brace in regex is deprecated, passed through in regex; marked
by <-- HERE in m/\${ <-- HERE ([^}]+)}/ at /usr/share/perl5/Debconf/Config.pm
line 30.
It is same bug as described here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=786705
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1633766/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325186] Re: gdebi-gtk crashed with UnicodeDecodeError in __getitem__(): 'utf-8' codec can't decode byte 0xeb in position 10: invalid continuation byte
*** This bug is a duplicate of bug 1302076 *** https://bugs.launchpad.net/bugs/1302076 ** This bug has been marked a duplicate of bug 1302076 gdebi-gtk crashed with UnicodeDecodeError in __getitem__(): 'utf-8' codec can't decode byte 0xed in position 26: invalid continuation byte -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1325186 Title: gdebi-gtk crashed with UnicodeDecodeError in __getitem__(): 'utf-8' codec can't decode byte 0xeb in position 10: invalid continuation byte Status in gdebi package in Ubuntu: New Bug description: Hello, gdebi-gtk crashed with the following error: gdebi-gtk crashed with UnicodeDecodeError in __getitem__(): 'utf-8' codec can't decode byte 0xeb in position 10: invalid continuation byte when installing the following deb package: http://eid.belgium.be/en/binaries/eid- mw_4.0.4r1253_amd64_tcm406-178472.deb I'll attach the crash report. The same problem has already been reported in a comment for bug #1301857 "gdebi-gtk crashed with UnicodeDecodeError in commit(): 'utf-8' codec can't decode byte 0xc3 in position 0: unexpected end of data", but this bug has status "Fix Released" so I'm creating a new bug report for this specific problem. The previous comment can be found here: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1301857/comments/5 Thanks a lot in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1325186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352322] Re: gdebi FTBFS when the locale is not en_US
** Attachment added: "Debdiff with the fix for Trusty" https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+attachment/4947390/+files/gdebi-debdiff ** Tags removed: utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1352322 Title: gdebi FTBFS when the locale is not en_US Status in gdebi package in Ubuntu: New Status in gdebi package in Debian: Fix Released Bug description: System: Xubuntu 14.04. Current gdebi version: 0.9.5.3ubuntu2 (from trusty-updates). Steps to reproduce: 1. Have some non-en_US locale currently set in your system. I have ru_RU for example. 2. sudo apt-get install dpkg-dev devscripts build-essential 3. sudo apt-get build-dep gdebi 4. apt-get source gdebi 5. cd gdebi-0.9.5.3ubuntu2 6. debuild -us -uc The build process will fail as shown in the first attachment. Now try the same with locale set to en_US (but do a cleanup first): 7. debuild clean 8. LC_ALL=en_US.UTF-8 debuild -us -uc The build process will succeed as shown in the second attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1352322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598488] Re: pcmanfm crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1494897 *** https://bugs.launchpad.net/bugs/1494897 ** Package changed: pcmanfm (Ubuntu) => glib2.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1494897 nautilus crashed with SIGABRT in g_assertion_message() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1598488 Title: pcmanfm crashed with SIGABRT in g_assertion_message() Status in glib2.0 package in Ubuntu: New Bug description: pcmanfm crashed with SIGABRT in g_assertion_message() How to reproduce: Open PCManFM to any directory, modify any file in that directory, then save from your editor, and PCManFM will crash. This only seems to happen some of the time. Xubuntu 16.04, PCManFM 1.2.4-1 System info: Description: Ubuntu 16.04 LTS Release: 16.04 pcmanfm: Installed: 1.2.4-1 Candidate: 1.2.4-1 Version table: *** 1.2.4-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status Possibly related: https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/1598360 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1598488/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached
** Summary changed: - nautilus crashed with SIGABRT in g_assertion_message() + various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Confirmed Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1529283] Re: Crash on opening with corrupted picture
*** This bug is a duplicate of bug 1494897 *** https://bugs.launchpad.net/bugs/1494897 ** Package changed: shotwell (Ubuntu) => glib2.0 (Ubuntu) ** This bug has been marked a duplicate of bug 1494897 nautilus crashed with SIGABRT in g_assertion_message() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1529283 Title: Crash on opening with corrupted picture Status in glib2.0 package in Ubuntu: New Bug description: # Context Due to some problem I don't understand now, Shotwell crashes while updating pictures metadata, resulting in empty or corrupted files. [But that's not the point of this report. I may open a new ticket when I understand the root cause.] # What happens it's that Shotwell now refuses to start, and report following error: joel@babasse-jojo:~$ shotwell L 2835 2015-12-25 20:14:36 [CRT] PhotoMonitor.vala:1069: Unable to reimport [9532] /home/joel/Images/2015-03-08 - déménagement à Pau/20150306_17.jpg due to master file changing: Fin précoce de flux inattendue ** GLib-GIO:ERROR:/build/glib2.0-ajuDY6/glib2.0-2.46.1/./gio/glocalfilemonitor.c:433:g_file_monitor_source_handle_event: code should not be reached Abandon (core dumped) Please find the corrupted file attached (even if it's 0B long). # What I would expect to happen Shotwell should detect that the file is corrupted, and ignore it / raise an alert / tag it as missing or corrupted. # Versions description Shotwell package version: 0.22.0-0ubuntu5 Xubuntu version : 15.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1529283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1494897] Re: nautilus crashed with SIGABRT in g_assertion_message()
** This bug is no longer a duplicate of bug 1497743 nautilus crashed with SIGABRT in g_assertion_message() ** Package changed: nautilus (Ubuntu) => glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1494897 Title: various apps abort on assertion - g_file_monitor_source_handle_event: code should not be reached Status in glib2.0 package in Ubuntu: Confirmed Bug description: I was opening "War Thunder"- Steam game and when I changed settings in game and it restarted I saw also in desktop error-message. I do not remember did I have anything from "nautilus" open. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu10 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Sep 11 22:00:01 2015 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2015-09-11 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150910) ProcCmdline: nautilus -n Signal: 6 SourcePackage: nautilus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_file_monitor_source_handle_event () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare saned scanner sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1494897/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
