Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • evolution evolution
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 279
    • Issues 279
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOME
  • evolutionevolution
  • Issues
  • #1783

Closed
Open
Created Jan 22, 2022 by Hu Jialun@SuibianP

EShell not emitting activate signal

EShell does not emit the activate signal to the primary instance on spawning another instance, while its parent class GtkApplication does so.

This seems to be due to Evolution directly using gtk_main instead of g_application_run, which in turn is responsible to call g_application_activate and emit the signal.

This makes it hard if not impossible for a module to hook onto the launch of an instance (primary or not). Also, the doc is misleading in this respect by not pointing out this behaviour with this inherited signal.

Edited Jan 23, 2022 by Hu Jialun
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking