Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • L libwnck
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 111
    • Issues 111
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • libwnck
  • Issues
  • #155
Closed
Open
Issue created Oct 16, 2022 by Evan Maddock@EbonJaeger

Calling `wnck_set_default_icon_size` can segfault

With the new invalidate_icons() code here, self->screens might not be initialized, causing a segfault. wnck_set_default_icon_size and wnck_setmini_icon_sizegets or creates a new WnckHandle, but this does not initialize thescreens` member, as far as I can tell. It looks like the previous code1 explicitly got the default screen and then iterates over its windows.

This causes bamf/bamfdaemon to break, which uses libwnck for window tracking, and thus in turn causes other applications using bamf to break, such as Plank.

  1. 72fee2a5 ↩

Assignee
Assign to
Time tracking