Let's reject this one then...
** Changed in: banshee (Ubuntu)
Status: Unconfirmed => Rejected
--
Banshee uses hardcoded fonts instead of system fonts
https://launchpad.net/bugs/93442
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
Aaron, in Banshee itself everything is fine.
--
Banshee uses hardcoded fonts instead of system fonts
https://launchpad.net/bugs/93442
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I posted the notification-daemon bug here:
https://launchpad.net/ubuntu/+source/banshee/+bug/93441
--
Banshee uses hardcoded fonts instead of system fonts
https://launchpad.net/bugs/93442
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-
After further inspection, it seems Banshee is not at fault.
** Attachment added: "Banshee DBUS log"
http://librarian.launchpad.net/6851967/bansheelog.txt
--
Banshee uses hardcoded fonts instead of system fonts
https://launchpad.net/bugs/93442
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
Banshee does not hard code any fonts. There's not even a way to do that
with the notification APIs. Banshee literally just sends the string of
text for what is currently playing. I doubt this is a Banshee issue -
does the correct text show up in the track information area in the main
Banshee UI?
-
This is a screenshot of a broken notification without the DejaVu fonts
installed. Installing the DejaVu fonts is a simple workaround. But
having the same font installed twice (DejaVu&Vera) is silly.
Banshee shouldn't hardcode this font!
** Attachment added: "Banshee Broken notification"
http:/
