[Bug 880952] Re: Evince prints gdk critical failings on console output
I found a workaround in case anyone's interested. By redirecting stderr to a file. It would be something like: gnome-open myfile.pdf 2 FileWithAllTheWarnings rm FileWithAllTheWarnings Doesn't fix the problem, but at least you can now open pdf files from the terminal without getting all those warnings. Hope it helps. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/880952 Title: Evince prints gdk critical failings on console output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/880952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 890751] [NEW] Error message when opening pdf: Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed
Public bug reported: Every time I open a pdf file through the terminal (using gnome-open or evince) this message appears several times: (evince: ) Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed This started happening after upgrading to 11.10 evince: Installed: 3.2.1-0ubuntu2 Candidate: 3.2.1-0ubuntu2 Version table: *** 3.2.1-0ubuntu2 0 500 http://ar.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 3.2.0-0ubuntu1 0 500 http://ar.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/890751 Title: Error message when opening pdf: Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/890751/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 874299] Re: in gedit external tools' names can not be edited
In case anyone is interested, there's a workaround: it's possible to edit the file that contains the external tool. On gedit3 user generated external tools are stored in ~/.config/gedit/tools There you can change the name of the file and, more importantly, change the name of the external tool. To do that simple open the file and edit the line that says '# Name=New Tool' by putting the name of your choice. Sorry if this is not the place to post this information, but I thought someone who stumbled upon this bug might find it useful. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/874299 Title: in gedit external tools' names can not be edited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/874299/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 874299] Re: in gedit external tools' names can not be edited
I have the same problem in both the External Tools and the Snippets plugin -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/874299 Title: in gedit external tools' names can not be edited To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/874299/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
