[Bug 1899236] Re: gnome-shell crashed with SIGABRT after connecting external monitor

*** This bug is a duplicate of bug 1898005 *** https://bugs.launchpad.net/bugs/1898005 ** Attachment removed: "JournalErrors.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1899236/+attachment/5420299/+files/JournalErrors.txt -- You received this bug notification because

[Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

I cannot reproduce it repeatedly. Currently gnome-tweaks opens without crashing gnome-shell. ** Attachment added: "Crash file for a previous journalctl /usr/bin/gnome-shell -b output"

[Bug 1796606] Re: gnome-shell crashed with SIGSEGV in st_widget_get_theme_node → ffi_call_unix64 → ffi_call → gjs_invoke_c_function → function_call

Managed to reproduce the crash by launching gnome-tweaks. Here is the log from just before the crash to after logging back in. ** Attachment added: "Output of journalctl /usr/bin/gnome-shell -b"

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

** Bug watch added: freedesktop.org Bugzilla #10881 https://bugs.freedesktop.org/show_bug.cgi?id=10881 ** Changed in: poppler Status: Invalid = Unknown ** Changed in: poppler Remote watch: freedesktop.org Bugzilla #22439 = freedesktop.org Bugzilla #10881 -- PDF file containing

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

** Attachment added: Example pdf file http://launchpadlibrarian.net/28234174/Etiketes_pvz.pdf -- PDF file containing bar-codes is rendered incorrectly https://bugs.launchpad.net/bugs/390991 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

** Attachment added: Expected behavior http://launchpadlibrarian.net/28234185/okular.png -- PDF file containing bar-codes is rendered incorrectly https://bugs.launchpad.net/bugs/390991 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to

[Bug 390991] [NEW] PDF file containing bar-codes is rendered incorrectly

Public bug reported: Description:Ubuntu karmic (development branch) Release:9.10 evince: Installed: 2.27.3-0ubuntu1 Candidate: 2.27.3-0ubuntu1 Version table: *** 2.27.3-0ubuntu1 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

** Attachment added: Current behavior in evince http://launchpadlibrarian.net/28234181/evince.png -- PDF file containing bar-codes is rendered incorrectly https://bugs.launchpad.net/bugs/390991 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

** Attachment added: incorrect nautilus thumbnail http://launchpadlibrarian.net/28234203/thumbnail.png -- PDF file containing bar-codes is rendered incorrectly https://bugs.launchpad.net/bugs/390991 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

** Attachment added: Correct behavior in xpdf http://launchpadlibrarian.net/28234204/xpdf.png -- PDF file containing bar-codes is rendered incorrectly https://bugs.launchpad.net/bugs/390991 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is

[Bug 390991] Re: PDF file containing bar-codes is rendered incorrectly

But doesn't Okular use poppler as the pdf backend too and doesn't have this problem? -- PDF file containing bar-codes is rendered incorrectly https://bugs.launchpad.net/bugs/390991 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. --

[Bug 148603] Re: wrong entry in default gconf for gnome-screensaver

/var/lib/gconf/debian.defaults/%gconf-tree.xml is generated from files in: /usr/share/gconf/defaults by sudo update-gconf-defaults so the problem is (was) in some file from /usr/share/gconf/defaults or in the program update-gconf-defaults (in gconf2 package) -- wrong entry in default gconf