Telegram has two entries in Notification system settings

Bug #1434181 reported by Michał Karnicki
58
This bug affects 12 people
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Pat McGowan
Telegram app
Invalid
High
Unassigned
ubuntu-system-settings (Ubuntu)
Fix Released
High
Roberto Alsina
ubuntu-system-settings (Ubuntu RTM)
Fix Released
Undecided
Roberto Alsina

Bug Description

Steps to reproduce:
1. Open Settings app
2. Open notifications

Expected:
Telegram has one entry

Actual:
Telegram has two entries, one of which doesn't have a picture.

Related branches

Revision history for this message
amiguetemelide (amiguetemelide) wrote :

the same bug, one of them with telegram logo, and the other with white square logo

Changed in libqtelegram:
status: New → Confirmed
Michał Karnicki (karni)
Changed in libqtelegram:
status: Confirmed → Triaged
importance: Undecided → Medium
Michał Karnicki (karni)
Changed in libqtelegram:
importance: Medium → High
Revision history for this message
Pat McGowan (pat-mcgowan) wrote :

If there is a push hook and both a scope and app exist for the same hook, we want to only have one entry
But we still want to show an entry when there is only a scope.
So we essentially want to do this er package and not per app and per scope

Changed in ubuntu-system-settings (Ubuntu):
assignee: nobody → Roberto Alsina (ralsina)
Changed in canonical-devices-system-image:
assignee: nobody → Pat McGowan (pat-mcgowan)
importance: Undecided → High
milestone: none → ww13-ota
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ubuntu-system-settings (Ubuntu):
status: New → Confirmed
Changed in ubuntu-system-settings (Ubuntu):
importance: Undecided → High
Changed in canonical-devices-system-image:
status: Confirmed → In Progress
Changed in ubuntu-system-settings (Ubuntu):
status: Confirmed → In Progress
Changed in ubuntu-system-settings (Ubuntu RTM):
assignee: nobody → Roberto Alsina (ralsina)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20150331.2-0ubuntu1

---------------
ubuntu-system-settings (0.3+15.04.20150331.2-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * Resync trunk.

  [ Roberto Alsina ]
  * Use per-package notification settings instead of per-app and per-
    scope. (LP: #1434181)
 -- CI Train Bot <email address hidden> Tue, 31 Mar 2015 19:39:17 +0000

Changed in ubuntu-system-settings (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-system-settings - 0.3+15.04.20150331.2~rtm-0ubuntu1

---------------
ubuntu-system-settings (0.3+15.04.20150331.2~rtm-0ubuntu1) 14.09; urgency=medium

  [ CI Train Bot ]
  * New rebuild forced.

  [ Roberto Alsina ]
  * Use per-package notification settings instead of per-app and per-
    scope. (LP: #1434181)
 -- CI Train Bot <email address hidden> Tue, 31 Mar 2015 21:53:01 +0000

Changed in ubuntu-system-settings (Ubuntu RTM):
status: New → Fix Released
Michał Karnicki (karni)
Changed in libqtelegram:
status: Triaged → Invalid
Changed in canonical-devices-system-image:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.