[Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
Yep, works like a charm with 3.38.0-1ubuntu1.1 from groovy-proposed here as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1900729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900729] Re: gnome-terminal font settings show only italic version of ubuntu mono
Thanks for the speedy work! I'm afraid I'm registering problems with the update, however. I just got gir1.2-gtk-3.0 through -proposed, and whereas it works as intended in so far as I can now choose Ubuntu Mono in Gnome Terminal and get the regular font face, it seemingly introduces a bug where gnome- terminal crashes, when I try to select certain typefaces. For instance, when I open up Preferences of go to the font selection box, as soon as I click on e.g. "DejaVu Sans Mono", gnome-terminal just closes. When I open it again, it's still using the previously set font. The problem also occurs with "Inconsolata", but seemingly not with any other fonts I have installed, whether fonts that ship with Ubuntu or fonts I've installed on my own. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900729 Title: gnome-terminal font settings show only italic version of ubuntu mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1900729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)
@Sebastien: No, I've not noticed the bug for a long while. It must have been fixed in later Ubuntu versions somehow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)
I filed it here: https://bugzilla.gnome.org/show_bug.cgi?id=793914 ** Bug watch added: GNOME Bug Tracker #793914 https://bugzilla.gnome.org/show_bug.cgi?id=793914 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)
** Description changed: Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open when I'm logged on using Wayland. There's no problem using X. The error is very simple. I double click a PDF file in my file manager and expect it to open in Evince (Document Viewer). And mostly that's what happens, but after having opened a few files, it just stops working for some files. The error seldom occurs with the first PDF file I open after a reboot, but after I've opened a few files, the error pops up, but only for some files. Some files I can click and they open in Evince each time, whereas other files will never open in Evince. They open fine in other applications and under X. When I try to open the file from the command line, I get the following error message: pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ –\ Etymological\ Dictionary\ of\ Greek.pdf Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. If I rename the file (e.g. by adding the number "2" to the file name), make a copy or move it to another directory, it opens without problems. - However, after some uptime the renamed or new file will often fail to - open with the same error. + However, after some time the renamed or new file will fail to open with + the same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)
** Description changed: Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open when I'm logged on using Wayland. There's no problem using X. The error is very simple. I double click a PDF file in my file manager and expect it to open in Evince (Document Viewer). And mostly that's what happens, but after having opened a few files, it just stops working for some files. The error seldom occurs with the first PDF file I open after a reboot, but after I've opened a few files, the error pops up, but only for some files. Some files I can click and they open in Evince each time, whereas other files will never open in Evince. They open fine in other applications and under X. When I try to open the file from the command line, I get the following error message: pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ –\ Etymological\ Dictionary\ of\ Greek.pdf Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. - If I rename the file (e.g. by adding the number "2" to the file name) or - move it to another directory, it opens without problems. + If I rename the file (e.g. by adding the number "2" to the file name), + make a copy or move it to another directory, it opens without problems. + However, after some uptime the renamed or new file will often fail to + open with the same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743043] Re: Evince sometimes fails to open under Wayland (Protocol error)
** Description changed: Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open when I'm logged on using Wayland. There's no problem using X. The error is very simple. I double click a PDF file in my file manager and expect it to open in Evince (Document Viewer). And mostly that's what happens, but after having opened a few files, it just stops working for some files. The error seldom occurs with the first PDF file I open after a reboot, but after I've opened a few files, the error pops up, but only for some files. Some files I can click and they open in Evince each time, whereas other files will never open in Evince. They open fine in other applications and under X. When I try to open the file from the command line, I get the following error message: - pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ –\ Etymological\ Dictionary\ of\ Greek.pdf + pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ –\ Etymological\ Dictionary\ of\ Greek.pdf Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. If I rename the file (e.g. by adding the number "2" to the file name) or - move it to another dictionary, it opens without problems. + move it to another directory, it opens without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743043] [NEW] Evince sometimes fails to open under Wayland (Protocol error)
Public bug reported: Under Ubuntu 17.10 I find that Evince (3.26.0-1) often fails to open when I'm logged on using Wayland. There's no problem using X. The error is very simple. I double click a PDF file in my file manager and expect it to open in Evince (Document Viewer). And mostly that's what happens, but after having opened a few files, it just stops working for some files. The error seldom occurs with the first PDF file I open after a reboot, but after I've opened a few files, the error pops up, but only for some files. Some files I can click and they open in Evince each time, whereas other files will never open in Evince. They open fine in other applications and under X. When I try to open the file from the command line, I get the following error message: pinnerup@ergi:~$ evince Dropbox/Litteratur/Sprog/Græsk/Beekes\ \&\ van\ Beek\ –\ Etymological\ Dictionary\ of\ Greek.pdf Gdk-Message: Error 71 (Protocol error) dispatching to Wayland display. If I rename the file (e.g. by adding the number "2" to the file name) or move it to another dictionary, it opens without problems. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743043 Title: Evince sometimes fails to open under Wayland (Protocol error) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1743043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633819] Re: Some PyQt4 applications fail to start in Yakkety due to missing PyQt4-WebKit
@David: That worked! Thank you very much for your help. I hope the overarching issue is resolved soon :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633819 Title: Some PyQt4 applications fail to start in Yakkety due to missing PyQt4-WebKit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633819] Re: Some PyQt4 applications fail to start in Yakkety due to missing PyQt4-WebKit
@David: Thank you; that doesn't seem to work here, tho. When I run apt-get, it
replies with:
E: Version ‘4.11.4+dfsg-1build4’ for ‘python-qt4’ was not found
E: Version ‘4.11.4+dfsg-1build4’ for ‘python-qt4-sql’ was not found
It seems it doesn't have access to earlier versions that the installed one
("4.11.4+dfsg-2").
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to python-qt4 in Ubuntu.
https://bugs.launchpad.net/bugs/1633819
Title:
Some PyQt4 applications fail to start in Yakkety due to missing
PyQt4-WebKit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1633819] Re: Some PyQt4 applications fail to start in Yakkety due to missing QtWebKit
Wow, this is an unfortunate surprise after upgrading to 16.10. I cannot do without Anki. How did you perform the downgrade, David? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633819 Title: Some PyQt4 applications fail to start in Yakkety due to missing QtWebKit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-qt4/+bug/1633819/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445595] Re: Empty trash from Launcher results in Nautilus window opening
>This bug was fixed in the package nautilus - 1:3.18.2-1ubuntu1 Sounds good, but I wonder when this reaches Ubuntu then. Mine is currently at 1:3.14.2-0ubuntu13. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445595 Title: Empty trash from Launcher results in Nautilus window opening To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1445595/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 513644] Re: Does not log fsck invocations in /var/log/fsck/
Ehm, this bug is still here in trusty, more than four years after it was originally reported. And it does seem to be quite an essential thing, being able to see the output of your file system repair. Can it really be so hard to have fsck save the output somewhere? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/513644 Title: Does not log fsck invocations in /var/log/fsck/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/513644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 626943] Re: [Maverick] Flickering on Radeon - please cherry pick 646d2e9fbc41bf49075013009e9583bec4a51168
I've just installed Maverick on my desktop and have flickering as described here every few seconds on a totally clean installation. Changing resolution, frequency or Visual Effects setting doesn't help. My GFX card is an ATI Radeon X1600. Either this bug was not properly fixed and has resurfaced or a very similar bug has disappeared. -- [Maverick] Flickering on Radeon - please cherry pick 646d2e9fbc41bf49075013009e9583bec4a51168 https://bugs.launchpad.net/bugs/626943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 545443] Re: Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network
Confirmed after full install of 10.04 LTS on EEEPC 901. Everything seemingly works fine, but trying to connect (WPA2) I get repeated timeouts. Now and then, tho, it'll connect, but those are rare occasions. Apparently it works a bit better with unprotected networks. -- Lucid on Asus EEE PC 901 and 1000H fails to connect to any wireless network https://bugs.launchpad.net/bugs/545443 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
