Comment 9 for bug 1724115

good job

Em sáb., 11 de abr. de 2020 às 15:55, Launchpad Bug Tracker <
<email address hidden>> escreveu:

> This bug was fixed in the package brisk-menu - 0.6.0-1ubuntu1
>
> ---------------
> brisk-menu (0.6.0-1ubuntu1) focal; urgency=medium
>
> [ Mike Gabriel ]
> * debian/control:
> + Add Rules-Requires-Root: field and set it to no.
> + Bump Standards-Version: to 4.5.0. No changes needed.
>
> [ Martin Wimpress ]
> * debian/patches:
> + Add 1000_fix_crashes_on_menu_rebuild.patch. Hide menu when rebuilding
> menu items. (LP: #1724115)
> + Add 1001_recreate_applet_when_changing_type.patch. Re-create applet
> menu
> when changing window-type. (LP: #1724262)
> + Add 1002_fix_keyboard_navigation.patch. Allow keyboard navigation.
> (LP: #1821315)
>
> -- Martin Wimpress <email address hidden> Fri, 10 Apr 2020
> 22:05:42 +0100
>
> ** Changed in: brisk-menu (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1794862).
> https://bugs.launchpad.net/bugs/1724115
>
> Title:
> brisk-menu crashed while looking at items while a app was currently
> being installed
>
> Status in brisk-menu package in Ubuntu:
> Fix Released
>
> Bug description:
> Ubuntu version: Ubuntu 17.10
> Flavor: Ubuntu Mate
>
> mate-applet-brisk-menu:
> Installed: 0.4.5-1
> Candidate: 0.4.5-1
> Version table:
> *** 0.4.5-1 500
> 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64
> Packages
> 100 /var/lib/dpkg/status
>
>
> This occurred when I was browsing the menu as an item was being
> installed.
>
> Steps to recreate:
>
> 1. Open Software Boutique
> 2. Find an app that has not yet been installed
> 3. Click Install
> 4. Go to the queue
> 5. Click Install
> 6. While the app in installing open up the Brisk menu
> 7. Keep the menu open until the app completes installing
>
> Expected results: Application does not crash (As a user I do not expect
> the new application to be in the menu yet, but it might be nice to have
> this feature if possible)
> Actual results: Application crashes and must be reloaded.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: mate-applet-brisk-menu 0.4.5-1
> ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
> Uname: Linux 4.13.0-16-generic x86_64
> NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
> ApportVersion: 2.20.7-0ubuntu3
> Architecture: amd64
> CurrentDesktop: MATE
> Date: Mon Oct 16 20:36:15 2017
> Disassembly: => 0x555d00000000: Cannot access memory at address
> 0x555d00000000
> EcryptfsInUse: Yes
> ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
> InstallationDate: Installed on 2017-10-17 (0 days ago)
> InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64
> (20170926)
> ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu
> ProcEnviron:
> SHELL=/bin/bash
> XDG_RUNTIME_DIR=<set>
> PATH=(custom, no user)
> LANGUAGE=en_US
> LANG=en_US.UTF-8
> SegvAnalysis:
> Segfault happened at: 0x555d00000000: Cannot access memory at
> address 0x555d00000000
> PC (0x555d00000000) not located in a known VMA region (needed
> executable region)!
> SegvReason: executing unknown VMA
> Signal: 11
> SourcePackage: brisk-menu
> StacktraceTop:
> ?? ()
> ?? ()
> ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> gtk_list_box_insert () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
> g_cclosure_marshal_VOID__OBJECTv () from
> /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: brisk-menu crashed with SIGSEGV in gtk_list_box_insert()
> 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/brisk-menu/+bug/1724115/+subscriptions
>