[Bug 2064880] [NEW] Gimp crashed as I was closing the app

2024-05-05 Thread Adrian
Public bug reported:




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu3' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-OiuXZC/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu3) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 556954 - Thread 556954 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 557181]
[New LWP 556975]
[New LWP 556972]
[New LWP 556970]
[New LWP 556969]
[New LWP 556968]
[New LWP 556967]
[New LWP 556966]
[New LWP 556965]
[New LWP 556964]
[New LWP 556963]
[New LWP 556962]
[New LWP 556961]
[New LWP 556960]
[New LWP 556959]
[New LWP 556958]
[New LWP 556957]
[New LWP 556956]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7e6a0911ba9a in __GI___libc_read (nbytes=256, buf=0x7ffe1ddc50b0, fd=18) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id Frame 
* 1Thread 0x7e6a086a2640 (LWP 556954) "gimp-2.10"0x7e6a0911ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffe1ddc50b0, fd=18) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7e69de0006c0 (LWP 557181) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7e69dea006c0 (LWP 556975) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7e69dfe006c0 (LWP 556972) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7e69e98006c0 (LWP 556970) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7e69f24006c0 (LWP 556969) "gdbus"0x7e6a0911b4cd in 
__GI___poll (fds=0x7e69ac000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7e69f2e006c0 (LWP 556968) "gmain"0x7e6a0911b4cd in 
__GI___poll (fds=0x62eecd496990, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7e69f38006c0 (LWP 556967) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7e69fcc006c0 (LWP 556966) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7e69fd6006c0 (LWP 556965) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7e69fe0006c0 (LWP 556964) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7e69fea006c0 (LWP 556963) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7e69ff4006c0 (LWP 556962) "worker"   sy

[Bug 2012757] Re: Incorrect total system memory

2023-11-12 Thread Adrian Feliks
Changing units helped. Thanks

** Changed in: gnome-system-monitor (Ubuntu)
   Status: Incomplete => Invalid

** Information type changed from Public to Private

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/2012757

Title:
  Incorrect total system memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2012757/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2012757] [NEW] Incorrect total system memory

2023-03-24 Thread Adrian Feliks
Public bug reported:

Gnome System Monitor has been incorrectly showing the amount of RAM for
some time (months?). Based on the system logs, I was able to determine
that Gnome System Monitor has not been updated recently. So where is the
incorrect data coming from?

Gnome System Monitor:
RAM: 33.5 GB
SWAP: 1.5 GB

$ free
   totalusedfree  shared  buff/cache   available
Mem:3270654012241184 5677344 12234281478801211034196
Swap:1459904   0 1459904

Everything indicates that Gnome System Monitor as RAM, gives the amount of RAM 
+ SWAP. Why? Before that, the indications were correct - 32 GB RAM.
In addition, SWAP is shown separately.

** Affects: gnome-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Gnome System Monitor has been incorrectly showing the amount of RAM for
  some time (months?). Based on the system logs, I was able to determine
  that Gnome System Monitor has not been updated recently. So where is the
  incorrect data coming from?
  
  Gnome System Monitor:
  RAM: 33.5 GB
  SWAP: 1.5 GB
  
- 
  $ free
-totalusedfree  shared  buff/cache   
available
+    totalusedfree  shared  buff/cache   
available
  Mem:3270654012241184 5677344 122342814788012
11034196
  Swap:1459904   0 1459904
  
- Everything indicates that Gnome System Monitor as RAM, gives the amount of 
RAM + SWAP. Why?
+ Everything indicates that Gnome System Monitor as RAM, gives the amount of 
RAM + SWAP. Why? Before that, the indications were correct - 32 GB RAM.
  In addition, SWAP is shown separately.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/2012757

Title:
  Incorrect total system memory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/2012757/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 2000835] Re: After resuming work, only the external screen works.

2023-01-05 Thread Adrian Feliks
I am attaching the logs.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+attachment/5639364/+files/journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2000835

Title:
  After resuming work, only the external screen works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

2022-04-21 Thread Adrian Wilkins
So you can minimize this window and then have working Unity. If you
close it, your session ends.

This window belongs to a process of

/usr/libexec/gnome-session-failed

** Attachment added: "jammy-error-moved-aside.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+attachment/5582021/+files/jammy-error-moved-aside.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969357

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

2022-04-21 Thread Adrian Wilkins
Confirm (in KVM machines) that Unity works fine from gdm3 under Impish,
but a fresh VM of Jammy doesn't work with either lightdm or gdm for me.

I get to see a quick glimpse of the Unity desktop, then this fullscreen
splash error shows up

"Oh no! Something has gone wrong.

A problem has occurred and the system can't recover. 
All extensions have been disabled as a precaution."

Since it refers to extensions, I presume this is a part of GNOME Shell.

However... if you use the keyboard shortcut to left-split the window
(ctrl-super-left) ... you can see the Unity desktop is running. (I first
tried ctrl-alt-t to summon a terminal above it but the window is always-
on-top, I saw it lose focus though.)




** Attachment added: "jammy-gnome-shell-error.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+attachment/5582020/+files/jammy-gnome-shell-error.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969357

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1969357] Re: Unity7 crashes on Jammy with 22.04's gnome-session version

2022-04-20 Thread Adrian Wilkins
Is this a `gnome-session` issue? The source sayeth (@ gnome-
session/main.c:422)

/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
 * older versions of GDM,  other display managers, and startx,
 * set a fallback value if we don't find it set.
 */

There doesn't seem to be any other location in the code that sets
`XDG_CURRENT_DESKTOP` and this code hasn't changed between the two
versions listed above.

Is this because of a change to `gdm` ? Does it work if you switch to
lightdm?

`gdm` sets this from the session definition, which is patched into
gnome-session by

debian/patches/ubuntu/ubuntu-sessions.patch

(the patch file has changed between revisions but mostly to remove a
community session)


gdm fetches this @ daemon/gdm-session.c:2612  get_session_desktop_names()

filename = g_strdup_printf ("%s.desktop", get_session_name (self));
g_debug ("GdmSession: getting desktop names for file '%s'", filename);
keyfile = load_key_file_for_file (self, filename, NULL, NULL);
if (keyfile != NULL) {
  gchar **names;

  names = g_key_file_get_string_list (keyfile, 
G_KEY_FILE_DESKTOP_GROUP,
  "DesktopNames", NULL, NULL);

Can't see any obvious changes in GDM between Impish and Jammy that would
cause this just from looking at the diffs though.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1969357

Title:
  Unity7 crashes on Jammy with 22.04's gnome-session version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

2022-03-30 Thread Adrian Perez
(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
> 
> iris
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported modifier, resource creation failed.
> XXX: resource creation failed
> 
> zink
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=zink yelp
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> MESA-INTEL: warning: Performance support disabled, consider sysctl
> dev.i915.perf_stream_paranoid=0
> 
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

Zink will use internally lower-level parts from the Iris driver to access
the hardware, so at least this indicates that the issue is *below* the
OpenGL/GLES implementation. Could be EGL or hardware access, I suppose.

> i965
> 
> $ MESA_LOADER_DRIVER_OVERRIDE=i965 yelp
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)
> 
> WaylandCompositor requires eglBindWaylandDisplayWL,
> eglUnbindWaylandDisplayWL and eglQueryWaylandBuffer.
> Nested Wayland compositor could not initialize EGL
> libEGL warning: MESA-LOADER: failed to open i965: /usr/lib/dri/i965_dri.so:
> cannot open shared object file: No such file or directory (search paths
> /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri)

When a driver that was set explicitly like this fails to load, Mesa falls
back to using software rendering. This means you ended up here using the
swrast/llvmpipe driver, most likely (you can load “webkit://gpu” in the
Minibrowser or Epiphany to check this). This means that WebKit is most
likely using the GLX/EGL/OpenGL/GLES APIs correctly and the issue lies
somewhere in the Intel driver.

But the version of Mesa I am using here is the same as you and it works.
My suspicion is that one of the following is happening:

 * Patches applied by Debian/Ubuntu on top of Mesa are breaking the Intel
   driver. Here I am using Arch Linux, which does not apply any patches.
 * The Intel driver is being miscompiled somehow by the compiler toolchain
   shipped by Ubuntu. In case it helps, here Arch stable has GCC 11.2.0 as
   the default system compiler, so that's what gets used to build packages.
 * The bug could be related to your particular GPU model (and the
   corresponding code inside Mesa for it).

I hope this helps :)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

Title:
  [jammy regression] Evolution does not display message content anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1966418/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

2022-03-29 Thread Adrian Vovk
OK I found a way to fix it @ package time! I previously built webkitgtk
with -DENABLE_X11_TARGET=OFF. I tried building with
-DENABLE_X11_TARGET=ON (since this is the major difference between my
build and the gnome-build-meta build, aside from Mesa version), and now
it works properly

Seems like disabling the x11 backend also accidentally disables parts of
the Wayland backend somewhere

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

Title:
  [jammy regression] Evolution does not display message content anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1966418]

2022-03-29 Thread Adrian Vovk
I don't compile WebKit w/ X11 support so I can't tell you if running
epiphany w/ GDK_BACKEND=x11 helps anything

---

I do not see those EGL errors when I run epiphany on the host. However,
if I run the Epiphany flatpak with FLATPAK_GL_DRIVERS=host, I get

EGLDisplay Initialization failed: EGL_BAD_PARAMETER
Cannot create EGL context: invalid display (last error: EGL_SUCCESS)

but the webviews still show up (they're just sluggish). When running
with FLATPAK_GL_DRIVERS=host, the epiphany flatpak starts crashing when
opening about:gpu

---

Downgrading to Mesa 21.3.8 on the host does not solve the issue for me.
Not sure what's going on here, because Epiphany from Flathub (using Mesa
21.3.8, WebKitGTK 2.36.0) works perfectly fine in my environment

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1966418

Title:
  [jammy regression] Evolution does not display message content anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/1966418/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-30 Thread Adrian Barbuio
Okay, ever since I installed this bug fix, my mouse has been playing up.
First, dragging and dropping across windows exhibited errant behaviour,
such as dropping the dragging item in between box borders. Now, every
once in a while, my mouse's primary buttons switch. The original issue
has been resolved but this new issue is a little bit more problematic. I
am using Ubuntu 20.04 with @cristiano patch

** Attachment added: "lshw"
   
https://bugs.launchpad.net/ubuntu/focal/+source/mutter/+bug/1892440/+attachment/5415961/+files/specsaver.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-20 Thread Adrian Barbuio
@Marco thank you for your post regarding the test packages (comment
#50). This has almost solved the problem for me. I still get enlarged
text at the decryption password screen. Not a problem for me, but maybe
the information will help you guys.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1894231] [NEW] Gimp crashed navigating to file on another machine

2020-09-04 Thread Adrian Midgley
Public bug reported:

```
GNU Image Manipulation Program version 2.10.14
git-describe: GIMP_2_10_12-511-ga4f55d6c7e
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
7.4.0-1ubuntu1~18.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) 

using babl version 0.1.72 (compiled against version 0.1.72)
using GEGL version 0.4.18 (compiled against version 0.4.18)
using GLib version 2.56.4 (compiled against version 2.56.4)
using GdkPixbuf version 2.36.11 (compiled against version 2.36.11)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.40.14 (compiled against version 1.40.14)
using Fontconfig version 2.12.6 (compiled against version 2.12.6)
using Cairo version 1.15.10 (compiled against version 1.15.10)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 10761 - Thread 10761 #

[New LWP 10762]
[New LWP 10763]
[New LWP 10764]
[New LWP 10765]
[New LWP 10766]
[New LWP 10767]
[New LWP 10768]
[New LWP 10769]
[New LWP 10770]
[New LWP 10771]
[New LWP 10772]
[New LWP 10773]
[New LWP 10774]
[New LWP 10775]
[New LWP 10827]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7f5ac60ed394 in __libc_read (fd=19, buf=0x7ffdf786ef50, nbytes=256) at 
../sysdeps/unix/sysv/linux/read.c:27
  Id   Target Id Frame 
* 1Thread 0x7f5acaf1de00 (LWP 10761) "gimp" 0x7f5ac60ed394 in 
__libc_read (fd=19, buf=0x7ffdf786ef50, nbytes=256) at 
../sysdeps/unix/sysv/linux/read.c:27
  2Thread 0x7f5abcc98700 (LWP 10762) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7f5abc497700 (LWP 10763) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7f5abbc96700 (LWP 10764) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7f5ab3495700 (LWP 10765) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7f5abb495700 (LWP 10766) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7f5abac94700 (LWP 10767) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  8Thread 0x7f5aba493700 (LWP 10768) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7f5ab9c92700 (LWP 10769) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7f5ab9491700 (LWP 10770) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7f5ab8c90700 (LWP 10771) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7f5ab3fff700 (LWP 10772) "worker" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  13   Thread 0x7f5aabfff700 (LWP 10773) "gmain" 0x7f5ac5dffcf9 in 
__GI___poll (fds=0x56208d26ae60, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  14   Thread 0x7f5aab7fe700 (LWP 10774) "gdbus" 0x7f5ac5dffcf9 in 
__GI___poll (fds=0x7f5a5c0147c0, nfds=5, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  15   Thread 0x7f5a90a74700 (LWP 10775) "async" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  16   Thread 0x7f5a888ad700 (LWP 10827) "pool" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 16 (Thread 0x7f5a888ad700 (LWP 10827)):
#0  syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
No locals.
#1  0x7f5ac692f87a in g_cond_wait_until () from 
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#2  0x7f5ac68bc571 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
No symbol table info available.
#3  0x7f5ac6911b14 in ?? () from /usr/lib/x86_

[Bug 1892521] Re: Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2

2020-08-29 Thread Adrian Barbuio
I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behavior. I am
fairly certain this isn't an issue with my mouse and the issue emerged
just as this update occurred.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892521

Title:
  Shell text is too big in mutter 3.36.4-0ubuntu0.20.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2

2020-08-29 Thread Adrian Barbuio
I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behaviour. I am
fairly certain this isn't an issue with my mouse and the issue emerged
just as this update occured.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440

Title:
  Shell text is too small in mutter 3.36.4-0ubuntu0.20.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892440] Re: [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04

2020-08-26 Thread Adrian Barbuio
Thankyou Konrad, your comment #17, has solved this issue for me. I did
not hold the package at 6-0, though. Personal preference, but I feel
that accidentally updating and breaking it again is a simple fix, while
having a hold on a package that you have to remember to unhold could sit
in the background for ages.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892440

Title:
  [focal] Mutter 3.36.4-0ubuntu0.20.04.2 small text in Ubuntu 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892521] Re: UI bug - system fonts enlarge after every reboot

2020-08-26 Thread Adrian Barbuio
Hello Akhil

Thankyou for this suggestion and the time you have put in. I tried this,
and a few other workarounds from a few other forums, and they have all
failed for me. The only solution has been to roll back the recently
updated 'libmutter' package, as per comment #17 in
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440 using the
command:

sudo apt install libmutter-6-0=3.36.1-3ubuntu3
gir1.2-mutter-6=3.36.1-3ubuntu3

the post suggests to also hold the update using:

sudo apt-mark hold libmutter-6-0

I haven't needed to use this command, but I imagine any future update
will have to be checked for a solution if this isn't run. In any case,
this has provided a complete solution, with the login screen now also
back to normal.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892521

Title:
  UI bug - system fonts enlarge after every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1892521] Re: UI bug - system fonts enlarge after every reboot

2020-08-26 Thread Adrian Barbuio
0.walbert - where did you place these commands? I'm a little new to this
and I have been having the same problem.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892521

Title:
  UI bug - system fonts enlarge after every reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892521/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1875712] Re: Unusable graphics, nouveau + G73 (GEForce 7600)

2020-07-27 Thread Adrian Nida
Hi,  Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
display issue.  I also have the same graphics card:

>From lspci:
03:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT] 
(rev a1)

Is there any workaround I can perform to make this desktop usable? Other
than blowing away the install and going back to 19.10?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1875712

Title:
  Unusable graphics, nouveau + G73 (GEForce 7600)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1875712/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1879968] Re: copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

2020-06-29 Thread Adrian Jones
This bug is still happening ..   it really does render this whole
package unworkable ..  its equivalent to the computer not working at
all.   At least that way you know your data isn't being corrupted.   I'm
appalled at the cavalier attitude this bug is being treated...other
end itus ...   I agree more and more it appears to be an OS issue yet it
appears when only using word .. as well as outside word.

Either way some heads need to get together and fix the bug. It used to
be when a critical bug like this was encountered then the part at fault
was removed.. the bug fixed offline and then tested back in. It seems
the modern approach is the old micorshaft approach of let the users test
and fix the bug. If its NOT this then the people here should be putting
pressure on those whose area it is ..reporting bugs is difficult
enough without constantly being shunted around saying its somewhere else
you report it ..  (only to find you have to install software to prove
the bug was happening .. er.. it was happening before I had to install
mutter).

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1879968

Title:
  copy/paste still sometimes fails in LibreOffice on mutter 3.36.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1879968/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-25 Thread Adrian Jones
Incidentally this bug has been happening and someone suggested updating
Mutter to the latest version.

I had to install mutter to then update it to try and fix it  ..   so now
there are bugs due to software that was never installed in the first
place !!!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1852183

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)

2020-05-25 Thread Adrian Jones
This is still happening despite the Ubuntu 20.04LTS installation being
fully patched using Liveupdate as at 25 May 2020.

In LibreOffice I have to hit Cntrl C repeatedly (more than 2 times or
click the copy icon sometimes 9 times or more to get some data   and
this is just staying within Office so office related only.

In the desktop other attempts to copy also to other applications and WINE 
applications still results in failures. 
The fix therefore has not worked.   If mutter was changed and has rendered the 
computer useless (I regard it as such right now as it is highly unreliable and 
induces errors) then it should be removed until the module has been fixed and 
tested.  DO NOT get the users to fix the problem.. that is why users have been 
driven away from Microsoft.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1852183

Title:
  [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu
  19.10 & 20.04 (see comment 93)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839010] Re: Touchpad does not work after installing Ubuntu

2019-08-07 Thread Adrian Barbuio
** Attachment added: "list_devices"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281528/+files/list_devices

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1839010

Title:
  Touchpad does not work after installing Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839010] Re: Touchpad does not work after installing Ubuntu

2019-08-07 Thread Adrian Barbuio
Here are the logs:

** Attachment added: "journal"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281525/+files/journal

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1839010

Title:
  Touchpad does not work after installing Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839010] [NEW] Touchpad does not work after installing Ubuntu

2019-08-05 Thread Adrian Barbuio
Public bug reported:

I previously had Windows 10 on my protab laptop. After wiping the hard
drive and installing Ubuntu 19.04 on the device, the touchpad ceases to
respond at all. I am using an external mouse currently.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 02:39:36 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-22 (164 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1839010

Title:
  Touchpad does not work after installing Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1839006] [NEW] No sound is playing from this laptop

2019-08-05 Thread Adrian Barbuio
Public bug reported:

I recently installed Ubuntu 19.04 on this protab laptop. In the settings
menu the sound output shows a headphone and a multichannel output
option. There is no sound coming out of either system, despite there
being sound detection demonstrated in the sound bars in the output menu
moving with the playback audio. I have tried force
restarting/reinstalling Alsa mixer and pulse audio and all the obvious
things such as checking sound level settings.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:3.32.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug  6 02:09:12 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2019-02-22 (164 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to disco on 2019-08-04 (1 days ago)

** Affects: gnome-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1839006

Title:
  No sound is playing from this laptop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839006/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-05-10 Thread Adrian S.
The issue persists on 19.04.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1822665] [NEW] Brightness can't be changed from keyboard

2019-04-01 Thread Adrian
Public bug reported:

Brightness level can't be changed from keyboard with the Fn key and the
corresponding designated key. Other functions like changing volumes
involving the Fn key work perfectly. The only way I can change
brightness is from the status bar.

Current OS: Ubuntu 19.04 Disco Dingo (development branch)
Package version: gnome-shell 3.32.0-1ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 20:46:39 2019
DisplayManager: gdm3
InstallationDate: Installed on 2018-12-31 (91 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-03-29 (3 days ago)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1822665

Title:
  Brightness can't be changed from keyboard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822665/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-03-16 Thread Adrian S.
After seeing Alex's post, I tried installing 410.104-0ubuntu0~18.10.1 from 
ppa:graphics-drivers.
Using 4.18.0-16-generic kernel.

I find that when I use Intel profile, powertop reports the nvidia card as 0% 
active, and the setting in Tunables shows up as Good.
However, /proc/acpi/bbswitch reports as :01:00.0 ON, and the *fans* are 
spinning.

Turning the graphics card OFF with bbswitch, the fans stop spinning.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-03-01 Thread Adrian S.
> * If I understand correctly, the bug does not occur in Ubuntu 18.10.
The user can switch seamlessly between using the Intel or the Nvidia
discrete graphics card. Is this correct?

@jespestana
No, this bug is affecting me on 18.10.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

2019-02-10 Thread Adrian
I am facing the same issue in Ubuntu 18.10. The super key randomly stops
working and I loose control of all windows except for the active window,
which in some cases also stops working and cannot even do clicks there.
The workaround I found is to close all windows, lock the screen and the
problem solves for 5-10 min or so. But this is clearly impractical and I
can't really go on like this any further. I re-installed the OS but it
didn't solve the issue. I have a Lenovo T430s if that helps. Does anyone
found a solution to this yet? I'd appreciate it very much!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1181666

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

2019-01-31 Thread Adrian S.
I can confirm that installing nvidia-390 through the Ubuntu driver dialog, and 
then using nvidia-settings or prime-select to set intel keeps the nvidia card 
on for me on my GeForce 840M laptop.
I can also confirm Installing bbswitch-dkms and turning it off through bbswitch 
works.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1778011

Title:
  SRU: PRIME Power Saving mode draws too much power

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1300659]

2018-08-27 Thread Adrian Johnson
Problem is caused by _cairo_path_fixed_stroke_extents() returning wrong
extents.

-- 
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/1300659

Title:
  printed pdf file lacks item boxes

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1300659/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1300659]

2018-08-27 Thread Adrian Johnson
Created attachment 125087
Debug patch

This patch shows the problem is caused by
_cairo_path_fixed_stroke_extents().

If the operation is changed to a fill (change line 259 in the PDF from
"S" to "f") the box appears in the output.

-- 
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/1300659

Title:
  printed pdf file lacks item boxes

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1300659/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1300659]

2018-08-27 Thread Adrian Johnson
Created attachment 125086
Reduced test case

Reduced test case. This PDF strokes a single path of one of the boxes in
the original PDF. The original PDF draws the boxes with the fill-stroke
operator "B". I've replaced it with a stroke "S".

To reproduce:

pdftocairo -ps reduced-test-case.pdf out.ps

The output does not show the box.

-- 
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/1300659

Title:
  printed pdf file lacks item boxes

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1300659/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1725121] Re: package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-04-28 Thread Adrian Tritschler
During upgrade from 17.10 to 18.04 this happened to me

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1725121

Title:
  package desktop-file-utils 0.23-1ubuntu3 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1725121/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1765504] Re: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

2018-04-27 Thread Adrian King
Previous upgrades 16.04,16.10,17.04,17.10. Current 17.10 to 18.04

To get past the upgrade error , (Not sure if this is correct) but this
is what I did

sudo apt-get remove libp11-kit-gnome-keyring

I had previously additionally installed MATE desktop, so to avoid any conflicts 
I removed it too.
sudo apt-get remove mate-desktop
 
sudo apt-get update
sudo apt-get upgrade
sudo apt dist-upgrade
update-manager -d
The last part said said it was all up to date.

I don't know how to force the 18.04 upgrade to run again.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1765504

Title:
  package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1765504/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1765504] Re: package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1 (Multi-Arch: no) is not co-installable with libp11-kit-gnom

2018-04-27 Thread Adrian King
The upgrade threw this error and the upgrade did not complete

KeyError: '0604-libp11-kit-gnome-keyring'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 126, in 
_apt_pkg
return self._cache()[package]
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 224, in __getitem__
raise KeyError('The cache has no package named %r' % key)
KeyError: "The cache has no package named '0604-libp11-kit-gnome-keyring'"

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/apport/package_hook", line 48, in 
pr['SourcePackage'] = apport.packaging.get_source(options.package)
  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 159, in 
get_source
if self._apt_pkg(package).installed:
  File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 128, in 
_apt_pkg
raise ValueError('package %s does not exist' % package)
ValueError: package 0604-libp11-kit-gnome-keyring does not exist

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1765504

Title:
  package libp11-kit-gnome-keyring 3.18.3-0ubuntu2 failed to
  install/upgrade: libp11-kit-gnome-keyring:all 3.28.0.2-1ubuntu1
  (Multi-Arch: no) is not co-installable with libp11-kit-gnome-keyring
  which has multiple installed instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1765504/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1721637] Re: can't open system settings(Ubuntu 17.10), icon is visible but settings don't dislay

2017-12-16 Thread Adrian Apthorp
I had the same issue. In my case it turned out that gnome-control-center
had been uninstalled. I'm not sure why, but reinstalling fixed it.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1721637

Title:
  can't open  system settings(Ubuntu 17.10), icon is visible but
  settings don't dislay

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1721637/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726538] Re: Dual monitor configuration not saved across logout / login

2017-12-13 Thread Adrian
I have reported the bug on Gnome Bugzilla.
https://bugzilla.gnome.org/show_bug.cgi?id=791583

** Tags added: asked-to-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726538

Title:
  Dual monitor configuration not saved across logout / login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1726538] Re: Dual monitor configuration not saved across logout / login

2017-12-13 Thread Adrian
I have reported the bug on Gnome Bugzilla.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538

** Bug watch added: GNOME Bug Tracker #791583
   https://bugzilla.gnome.org/show_bug.cgi?id=791583

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1726538

Title:
  Dual monitor configuration not saved across logout / login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1712080] Re: wayland: blank additioanl screen in maximum resolution

2017-11-03 Thread Adrian
Fixed with Ubuntu 17.10.

** Changed in: gnome-session (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1712080

Title:
  wayland: blank additioanl screen in maximum resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1712080/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1724583] Re: gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid graphics

2017-10-31 Thread Adrian
I had the same problem with Intel + AMD tandem on a desktop. I solved it
by adding in /etc/environment:

MUTTER_ALLOW_HYBRID_GPUS=1

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1724583

Title:
  gdm3 in Ubuntu 17.10 doesn't list wayland sessions when using hybrid
  graphics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1712080] [NEW] wayland: blank additioanl screen in maximum resolution

2017-08-21 Thread Adrian
Public bug reported:

I use a docking station to which I have connected 2 screens: first one
directly through the display port, second through DVI connector (from
which signal passes DVI-HDMI converter and finally to the screen). In
default gnome session, the two extra screens are set in their maximum
resolution (2560x1440@60). In Wayland session, one the second screen
gets off although it is properly detected in the screen settings. In
order to make it work, I need to decrease its resolution (2048x1152).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-session-wayland 3.24.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Aug 21 15:31:50 2017
InstallationDate: Installed on 2015-04-02 (872 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: gnome-session
UpgradeStatus: Upgraded to zesty on 2017-04-18 (125 days ago)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug wayland-session zesty

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1712080

Title:
  wayland: blank additioanl screen in maximum resolution

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1712080/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

2017-07-22 Thread Adrian Fita
** Also affects: lightdm (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

2017-07-22 Thread Adrian Fita
Also see Bug #520546.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

2017-07-22 Thread Adrian Fita
On Linux Mint 18.2 (based on Ubuntu 16.04) I don't experience the issue
when using mdm as X display manager instead of lightdm.

So this has something to do with lightdm ?!!

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

2017-07-22 Thread Adrian Fita
A workaround that I found on reddit:
https://www.reddit.com/r/archlinux/comments/5620sf/alt_rightleft_arrow_keys_switching_to_virtual/d8g6ux5/

I created /etc/X11/xorg.conf.d/60-dontvtswitch.conf with the following
contents:

$ cat /etc/X11/xorg.conf.d/60-dontvtswitch.conf 
Section "ServerFlags"
Option "DontVTSwitch" "true"
EndSection

Now the Alt+Left/Right don't switch to the VT consoles.

But as a side effect it's not possible to switch to the VT consoles with
the usual Ctrl+Alt+F1...F12 shortcuts either.

So this is not good enough...

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1508146] Re: alt + left/right arrows switch between tty consoles, cannot disable

2017-07-22 Thread Adrian Fita
A workaround that I found on reddit:
https://www.reddit.com/r/archlinux/comments/5620sf/alt_rightleft_arrow_keys_switching_to_virtual/d8g6ux5/

I created /etc/X11/xorg.conf.d/60-dontvtswitch.conf with the following
contents:

$ cat /etc/X11/xorg.conf.d/60-dontvtswitch.conf 
Section "ServerFlags"
Option "DontVTSwitch" "true"
EndSection

Now the Alt+Left/Right don't switch to the VT consoles.

But as a side effect it's not possible to switch to the VT consoles with
the usual Ctrl+Alt+F1...F12 shortcuts either.

So this is not good enough...

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1508146

Title:
  alt + left/right arrows switch between tty consoles, cannot disable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556670] Re: Can't click on UI elements in gimp (intermittent)

2017-05-24 Thread adrian
That was running under Windows 8.1.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/556670

Title:
  Can't click on UI elements in gimp (intermittent)

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/556670/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 556670] Re: Can't click on UI elements in gimp (intermittent)

2017-05-24 Thread adrian
I had this, but it was with my mouse.  Don't know why, but I had to go
into Edit > Preferences > Input Devices > Reset Saved Input Device
Settings to Default Values.

Seems that that part of the configuration got corrupted somehow.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/556670

Title:
  Can't click on UI elements in gimp (intermittent)

To manage notifications about this bug go to:
https://bugs.launchpad.net/inkscape/+bug/556670/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1690759] [NEW] dns leak

2017-05-15 Thread Adrian
Public bug reported:

Using the network manager to set my OpenVPN I have a DNS leak after
connecting to my secured network which also provides Internet
connection.

I think solution is here: http://www.ubuntubuzz.com/2015/09/how-to-fix-
openvpn-dns-leak-in-linux.html

However, I didn't find in the network manager windows any place to set
those scripts.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: network-manager-openvpn-gnome 1.2.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: Unity:Unity7
Date: Mon May 15 10:32:38 2017
InstallationDate: Installed on 2015-04-02 (773 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to zesty on 2017-04-18 (26 days ago)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1690759

Title:
  dns leak

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1690759/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1453655] Re: desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox folder

2017-05-13 Thread Adrian King
Same issue in Ubuntu 17.04 (Unity)

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1453655

Title:
  desktop icons disappear on Ubuntu 15.04 when clicking Open Dropbox
  folder

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1453655/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1614554] [NEW] most recent part of graphs in resources tab is hidden

2016-08-18 Thread Adrian Pappas
Public bug reported:

On the resources tab, the most recent part of the monitoring graphs are
out of view. I am referring to the right side of the graph.

The problem becomes more prominent when the window is small
horizontally. As I scale it up horizontally, I can see more recent
measurements, but still there is a delay between the measurements and
the graph. When the window is at its minimum horizontal size, the delay
between measurement (text) and graph is more than 10 seconds, which is a
bit troublesome for visual real time system monitoring.

I might not be explaining this very well with words, so I'm attaching a
screenshot. Notice the usage of CPU3 (it has been at 100% for a few
seconds when I took the screenshot). I've circled the areas where the
problem occurs.

I've tested this problem with the CPU history and network history
graphs, it seems to be the same issue on both.

I am on Ubuntu 16.04.1 LTS . The version of gnome-system-monitor is
3.18.2-1 .

** Affects: gnome-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "screenshot of problem with the graphs"
   
https://bugs.launchpad.net/bugs/1614554/+attachment/4723482/+files/Screenshot%20from%202016-08-18%2017-11-34.png

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1614554

Title:
  most recent part of graphs in resources tab is hidden

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1614554/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1587968] [NEW] evince insentitive to typing in search, page, zoom, ect fields

2016-06-01 Thread Adrian
Public bug reported:

Thw way to reproduce:
Open an attached example_file.pdf file.
Press CTRL+F
Try to type something (in my case the field is insensitive, I can only paste 
some string).

The same problem with page and zoom fields.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10
Uname: Linux 4.4.0-23-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun  1 17:48:39 2016
InstallationDate: Installed on 2015-04-02 (426 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
SourcePackage: evince
UpgradeStatus: Upgraded to xenial on 2016-04-26 (36 days ago)

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-bug xenial

** Attachment added: "example_file.pdf"
   
https://bugs.launchpad.net/bugs/1587968/+attachment/4674463/+files/example_file.pdf

-- 
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/1587968

Title:
  evince insentitive to typing in search, page, zoom, ect fields

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1587968/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2016-01-16 Thread Adrian Johnson
Created attachment 120924
Check in ranges in ByteRange array v2

- renamed isInteger() to isIntOrInt64()
- added and use getIntOrInt64()

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2016-01-16 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #120)
> Ok, good, so Adrian can you commit your patch?

Pushed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2016-01-16 Thread Adrian Johnson
Created attachment 120924
Check in ranges in ByteRange array v2

- renamed isInteger() to isIntOrInt64()
- added and use getIntOrInt64()

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2016-01-16 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #120)
> Ok, good, so Adrian can you commit your patch?

Pushed

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2016-01-09 Thread Adrian Johnson
Created attachment 120889
Check in ranges in ByteRange array

This is an alternative to the patch in comment 108. It checks all ranges
in the ByteRange array.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2016-01-09 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #105)
> Created attachment 120434 [details] [review]
> Improve robustness of SignatureHandler::validateCertificate
> 
> This patch adds additional NULL-checking in
> SignatureHandler::validateCertificate() which avoids segfault for some
> signatures like the one contained here:
> http://www.gpo.gov/fdsys/pkg/BUDGET-2015-BUD/pdf/BUDGET-2015-BUD.pdf
> 
> It also removes a useless branch in validateCertificate()

Pushed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2016-01-09 Thread Adrian Johnson
Created attachment 120889
Check in ranges in ByteRange array

This is an alternative to the patch in comment 108. It checks all ranges
in the ByteRange array.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2016-01-09 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #105)
> Created attachment 120434 [details] [review]
> Improve robustness of SignatureHandler::validateCertificate
> 
> This patch adds additional NULL-checking in
> SignatureHandler::validateCertificate() which avoids segfault for some
> signatures like the one contained here:
> http://www.gpo.gov/fdsys/pkg/BUDGET-2015-BUD/pdf/BUDGET-2015-BUD.pdf
> 
> It also removes a useless branch in validateCertificate()

Pushed

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2016-01-09 Thread Adrian Johnson
I don't think we need to check if the byte range covers the entire
document. Our job, when verifying the signature, is to use the byte
ranges provided in the signature dictionary. It is up to the pdf
producer to ensure the byte range covers the entire document (excluding
the signature value).

All we need to do is ensure we check all bytes ranges in the ByteRange
array. We should also check that each byte range is within the file. eg
check that each offset is >= 0 and offset + length <= file size.

While it would be nice to check if the byte range covers the entire
document, poppler does not provide any easy way to determine the file
offsets of a dictionary value. This makes it difficult to check if the
excluded range only covers the signature value.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2016-01-09 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #114)
> I'm not very convinced by the naming of 
>   GBool isInteger() { return type == objInt || type == objInt64; }
> what do you think of 
>   isIntOrInt64() ?

I prefer a single word instead of isXXXorYYY() but I can appreciate that
isInteger() could easily be confused with isInt(). I'll change it to
isIntOrInt64().

I'll also add a corresponding getIntOrInt64() and replace the
"xxx.isInt64() ? xxx.getInt64() : xxx.getInt()" expressions with a single 
getter.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2016-01-09 Thread Adrian Johnson
I don't think we need to check if the byte range covers the entire
document. Our job, when verifying the signature, is to use the byte
ranges provided in the signature dictionary. It is up to the pdf
producer to ensure the byte range covers the entire document (excluding
the signature value).

All we need to do is ensure we check all bytes ranges in the ByteRange
array. We should also check that each byte range is within the file. eg
check that each offset is >= 0 and offset + length <= file size.

While it would be nice to check if the byte range covers the entire
document, poppler does not provide any easy way to determine the file
offsets of a dictionary value. This makes it difficult to check if the
excluded range only covers the signature value.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2016-01-09 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #114)
> I'm not very convinced by the naming of 
>   GBool isInteger() { return type == objInt || type == objInt64; }
> what do you think of 
>   isIntOrInt64() ?

I prefer a single word instead of isXXXorYYY() but I can appreciate that
isInteger() could easily be confused with isInt(). I'll change it to
isIntOrInt64().

I'll also add a corresponding getIntOrInt64() and replace the
"xxx.isInt64() ? xxx.getInt64() : xxx.getInt()" expressions with a single 
getter.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-31 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1: 
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all changes to the document,
> their use is not recommended."

This advice is for PDF producers. As a PDF consumer we should accept
PDFs that don't follow this advice.

https://en.wikipedia.org/wiki/Robustness_principle

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-31 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement

Pushed

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-31 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.

Done. I've also added a man page. If any further information that should
be in the man page can be posted here I can format it into the man page
format and push it out.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-31 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1: 
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all changes to the document,
> their use is not recommended."

This advice is for PDF producers. As a PDF consumer we should accept
PDFs that don't follow this advice.

https://en.wikipedia.org/wiki/Robustness_principle

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-31 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement

Pushed

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-31 Thread Adrian Johnson
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.

I'm still waiting for an answer to comment 79.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-31 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.

Done. I've also added a man page. If any further information that should
be in the man page can be posted here I can format it into the man page
format and push it out.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-31 Thread Adrian Johnson
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.

I'm still waiting for an answer to comment 79.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-24 Thread Adrian Johnson
What is the output of "pkg-config --cflags nss"?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-24 Thread Adrian Johnson
(In reply to Markus Kilås from comment #88)
> I found a workaround for my build issue by creating symlinks:
> /usr/include/nspr -> /usr/include/nspr4
> /usr/inclyde/nss -> /usr/include/nss3

Are you using configure or cmake? The nss pkgconfig file should contain
the correct include path.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1085526]

2015-10-24 Thread Adrian Johnson
What is the output of "pkg-config --cflags nss"?

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-24 Thread Adrian Johnson
(In reply to Markus Kilås from comment #88)
> I found a workaround for my build issue by creating symlinks:
> /usr/include/nspr -> /usr/include/nspr4
> /usr/inclyde/nss -> /usr/include/nss3

Are you using configure or cmake? The nss pkgconfig file should contain
the correct include path.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1085526]

2015-10-17 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.

I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for the other formats. I don't want pdfsig to
end up in the same situation.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-17 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.

I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for the other formats. I don't want pdfsig to
end up in the same situation.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1412916]

2015-10-12 Thread Adrian Johnson
(In reply to Martin McDowell from comment #8)
> It has been a year since a last post of this bug but I am still getting this
> problem in October 2015. I have Ubuntu 14.04. The PDF is viewed in the
> default Evince document viewer 3.10.3

The fix is in poppler 0.28 released in Nov 2014.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1412916

Title:
  evince: Bad PDF rendering: invalid font scale

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1412916/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #74)
> (In reply to Adrian Johnson from comment #73)
> > (In reply to Albert Astals Cid from comment #72)
> > > > Large file support.
> > > 
> > > Do you think this should be a blocker for the initial release or something
> > > we can improve later?
> > 
> > I think it should be included.
> 
> Do you have any file like that or a way to create it so the guys can test it?

I don't have a file. Bug 44085 contains a large file test case. But I
don't know how to sign it.

Implementing large file support is simply a case of using obj.isInt64()/
obj.getInt64() when getting the range offsets.

In addition, the code should avoid reading the entire range into memory
instead processing it in smaller chunks. From a quick look a the nss
headers it appears to have support for incremental hashing. This is good
practice even for < 2GB files as I have seen scanned PDFs that are in
the 100's of MB range.

I don't mind adding the getInt64() stuff myself as that is easy to do
without needing to understand the rest of the code. But the incremental
hashing would best be done by the original developer of the patch.

So at a a minimum if we can get the incremental hashing in then I can
sort out the rest of the 64-bit support.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-10 Thread Adrian Johnson
(In reply to Adam Reichold from comment #77)
> Some minor suggestions:
> 
> * The naming of BLOCK_SIZE and block_len in hashSignedDataBlock seems
> misleading to me, maybe CHUNK_SIZE and block_len?
> 
> * The method hashSignedDataBlock could probably be replaced by a static
> function taking the stream and the handler? This should give the compiler
> more optimization possibilities than if it is visible in other translation
> units.
> 
> * I think the while loop within could become a for loop for better
> readability with the case reduced to computing the number of bytes to read
> instead of two separate calls to doGetChars and updateHash.

I don't think there is much benefit in making that function a static. It
is not something that is called a frequently from an inner loop.

I think the function would read better as "hashSignedByteRange" as "byte
range" is the terminology used in the PDF reference section in
signatures. Instead of setting the stream offset before calling this
function it would better easier to understand the code if the function
took an offset and length.

I agree that the two calls to doGetChars and updateHash should be merged
but I don't think a for loop is the best way to process loops where the
increment is not exactly the same on each iteration. Maybe something
like this:

  void FormFieldSignature::hashSignedByteRange(SignatureHandler *handler,
 Goffset start, Goffset len)
  {
const int CHUNK_SIZE = 4096;
unsigned char buffer[CHUNK_SIZE];
Goffset i = 0;
int byte_count = CHUNK_SIZE;

doc->getBaseStream()->setPos(start);
while (i < len)
{
  if (i + CHUNK_SIZE > len)
byte_count = len - i;

  doc->getBaseStream()->doGetChars(byte_count, buffer);
  handler->updateHash(buffer, byte_count);
  i += byte_count;
}
  }

I renamed the "signed_data_buffer" to "buffer" as whenever I see
"signed" in C/C++ I think of the integer type. "unsigned char
signed_data_buffer" is confusing to read.

I would prefer the buffer be moved out to the class. It is better not to
allocate large buffers on the stack. We may later increase the buffer
size.

I don't mind if we fix all this later. It doesn't have to hold up the
initial release.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-10 Thread Adrian Johnson
+  r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
+  r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
+  r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
 
According the PDF Reference, the ByteRange array contains pairs of 
(offset,length).

Why do we ignore the first offset and later assume it is 0? Why do we
assume there are exactly two pairs.

I only skimmed over the digital signatures section so maybe I missed
something.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #72)
> > Large file support.
> 
> Do you think this should be a blocker for the initial release or something
> we can improve later?

I think it should be included.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #70)
> So we have two things missing, right?
>  * Enabling the use of other keystores
>  * The name of the pdfsigverify tool
> 
> 
> I think the enabling the use of other keystores is important but maybe not
> critical for the first release.
> 
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?
> 
> 
> Did i forget something?

Large file support.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #70)
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?

This is the only thing left that I think needs fixing before the initial
release. A couple of questions:

- Given that we want to keep the option open for using pdfsig to perform
other signature operations, should the default behavior when only a pdf
file is specified be to verify the signature? Or should we just indicate
whether the pdf is signed and use an option to enable verification?

- Is '-c' the best option name for "don't perform certificate
validation"?

We also need a man page.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #70)
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?

This is the only thing left that I think needs fixing before the initial
release. A couple of questions:

- Given that we want to keep the option open for using pdfsig to perform
other signature operations, should the default behavior when only a pdf
file is specified be to verify the signature? Or should we just indicate
whether the pdf is signed and use an option to enable verification?

- Is '-c' the best option name for "don't perform certificate
validation"?

We also need a man page.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-10 Thread Adrian Johnson
(In reply to Adam Reichold from comment #77)
> Some minor suggestions:
> 
> * The naming of BLOCK_SIZE and block_len in hashSignedDataBlock seems
> misleading to me, maybe CHUNK_SIZE and block_len?
> 
> * The method hashSignedDataBlock could probably be replaced by a static
> function taking the stream and the handler? This should give the compiler
> more optimization possibilities than if it is visible in other translation
> units.
> 
> * I think the while loop within could become a for loop for better
> readability with the case reduced to computing the number of bytes to read
> instead of two separate calls to doGetChars and updateHash.

I don't think there is much benefit in making that function a static. It
is not something that is called a frequently from an inner loop.

I think the function would read better as "hashSignedByteRange" as "byte
range" is the terminology used in the PDF reference section in
signatures. Instead of setting the stream offset before calling this
function it would better easier to understand the code if the function
took an offset and length.

I agree that the two calls to doGetChars and updateHash should be merged
but I don't think a for loop is the best way to process loops where the
increment is not exactly the same on each iteration. Maybe something
like this:

  void FormFieldSignature::hashSignedByteRange(SignatureHandler *handler,
 Goffset start, Goffset len)
  {
const int CHUNK_SIZE = 4096;
unsigned char buffer[CHUNK_SIZE];
Goffset i = 0;
int byte_count = CHUNK_SIZE;

doc->getBaseStream()->setPos(start);
while (i < len)
{
  if (i + CHUNK_SIZE > len)
byte_count = len - i;

  doc->getBaseStream()->doGetChars(byte_count, buffer);
  handler->updateHash(buffer, byte_count);
  i += byte_count;
}
  }

I renamed the "signed_data_buffer" to "buffer" as whenever I see
"signed" in C/C++ I think of the integer type. "unsigned char
signed_data_buffer" is confusing to read.

I would prefer the buffer be moved out to the class. It is better not to
allocate large buffers on the stack. We may later increase the buffer
size.

I don't mind if we fix all this later. It doesn't have to hold up the
initial release.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #74)
> (In reply to Adrian Johnson from comment #73)
> > (In reply to Albert Astals Cid from comment #72)
> > > > Large file support.
> > > 
> > > Do you think this should be a blocker for the initial release or something
> > > we can improve later?
> > 
> > I think it should be included.
> 
> Do you have any file like that or a way to create it so the guys can test it?

I don't have a file. Bug 44085 contains a large file test case. But I
don't know how to sign it.

Implementing large file support is simply a case of using obj.isInt64()/
obj.getInt64() when getting the range offsets.

In addition, the code should avoid reading the entire range into memory
instead processing it in smaller chunks. From a quick look a the nss
headers it appears to have support for incremental hashing. This is good
practice even for < 2GB files as I have seen scanned PDFs that are in
the 100's of MB range.

I don't mind adding the getInt64() stuff myself as that is easy to do
without needing to understand the rest of the code. But the incremental
hashing would best be done by the original developer of the patch.

So at a a minimum if we can get the incremental hashing in then I can
sort out the rest of the 64-bit support.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #72)
> > Large file support.
> 
> Do you think this should be a blocker for the initial release or something
> we can improve later?

I think it should be included.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-10 Thread Adrian Johnson
+  r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
+  r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
+  r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
 
According the PDF Reference, the ByteRange array contains pairs of 
(offset,length).

Why do we ignore the first offset and later assume it is 0? Why do we
assume there are exactly two pairs.

I only skimmed over the digital signatures section so maybe I missed
something.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-10-10 Thread Adrian Johnson
(In reply to Albert Astals Cid from comment #70)
> So we have two things missing, right?
>  * Enabling the use of other keystores
>  * The name of the pdfsigverify tool
> 
> 
> I think the enabling the use of other keystores is important but maybe not
> critical for the first release.
> 
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?
> 
> 
> Did i forget something?

Large file support.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-09-26 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #63)
> I also thought of adding the feature to pdfinfo but it seems wrong to mix up
> something which performs various computations and relies on external state
> (NSS cert DB) to pdfinfo which just reads metadata from the file itself.

pdfinfo already performs various computations. If the file is encrypted
it has to decrypt the objects to read the file. Reading from other
sources is not an issue if a switch is used to enable the signature
checking.

It seems pointless to me to add an entire new utility to perform one
function that can be enabled by adding a switch to pdfinfo.

I'll leave it to Albert decide. But if we keep pdfsigverify I suggest
making it more generic to allow for the possibility of later adding the
capability to sign pdfs. eg call it pdfsig and if verifying signatures
it not a fast operation, maybe enable the check with a switch and make
the default operation (ie no switch specified) report whether the pdf
contains a signature.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-09-26 Thread Adrian Johnson
(In reply to Andre Guerreiro from comment #63)
> I also thought of adding the feature to pdfinfo but it seems wrong to mix up
> something which performs various computations and relies on external state
> (NSS cert DB) to pdfinfo which just reads metadata from the file itself.

pdfinfo already performs various computations. If the file is encrypted
it has to decrypt the objects to read the file. Reading from other
sources is not an issue if a switch is used to enable the signature
checking.

It seems pointless to me to add an entire new utility to perform one
function that can be enabled by adding a switch to pdfinfo.

I'll leave it to Albert decide. But if we keep pdfsigverify I suggest
making it more generic to allow for the possibility of later adding the
capability to sign pdfs. eg call it pdfsig and if verifying signatures
it not a fast operation, maybe enable the check with a switch and make
the default operation (ie no switch specified) report whether the pdf
contains a signature.

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 740506]

2015-09-19 Thread Adrian Johnson
I don't think NSS should be mandatory. It is not required for rendering
PDFs.  configure/cmake should include NSS in the "building poppler with
support for" summary.

>  byte_range->arrayGet(1, &r2);
>  byte_range->arrayGet(2, &r3);
>  byte_range->arrayGet(3, &r4);
>
>  unsigned int signed_data_len = r2.getInt()+r4.getInt();
>  unsigned char *to_check = (unsigned char *)gmalloc(signed_data_len);
>
>  //Read the 2 slices of data that are signed
>  doc->getBaseStream()->setPos(0);
>  doc->getBaseStream()->doGetChars(r2.getInt(), to_check);
>  doc->getBaseStream()->setPos(r3.getInt());
>  doc->getBaseStream()->doGetChars(r4.getInt(), to_check+r2.getInt());

This does not support large files (> 2GB). The code should check if the
objects in byte_range are int64 and use the Goffset type for setting
file offsets.

It would be better to process the range in chunks instead of reading the
entire range into a buffer. We don't know how big the range could be and
it is not necessary to read it all at once as
HASH_Begin/HASH_Update/HASH_End can be used to process it in chunks.

I would prefer it if all the NSS includes were only included in the .cc
files similar to what we do with the image formats (JPEG2000Stream.h,
JpegWriter.h etc). It speeds up compilation, avoids clashes with other
include files, and makes it easier to replace NSS and/or support other
security libraries if we choose to do so in future.

The pdfsigutil utility doesn't seem to do much. Unless there are plans
to add a lot of extra options and functionality would it be better to
add an option to pdfinfo to check signatures instead of adding a new
util?

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506

Title:
  verify digital signatures

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/740506/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 1085526]

2015-09-19 Thread Adrian Johnson
I don't think NSS should be mandatory. It is not required for rendering
PDFs.  configure/cmake should include NSS in the "building poppler with
support for" summary.

>  byte_range->arrayGet(1, &r2);
>  byte_range->arrayGet(2, &r3);
>  byte_range->arrayGet(3, &r4);
>
>  unsigned int signed_data_len = r2.getInt()+r4.getInt();
>  unsigned char *to_check = (unsigned char *)gmalloc(signed_data_len);
>
>  //Read the 2 slices of data that are signed
>  doc->getBaseStream()->setPos(0);
>  doc->getBaseStream()->doGetChars(r2.getInt(), to_check);
>  doc->getBaseStream()->setPos(r3.getInt());
>  doc->getBaseStream()->doGetChars(r4.getInt(), to_check+r2.getInt());

This does not support large files (> 2GB). The code should check if the
objects in byte_range are int64 and use the Goffset type for setting
file offsets.

It would be better to process the range in chunks instead of reading the
entire range into a buffer. We don't know how big the range could be and
it is not necessary to read it all at once as
HASH_Begin/HASH_Update/HASH_End can be used to process it in chunks.

I would prefer it if all the NSS includes were only included in the .cc
files similar to what we do with the image formats (JPEG2000Stream.h,
JpegWriter.h etc). It speeds up compilation, avoids clashes with other
include files, and makes it easier to replace NSS and/or support other
security libraries if we choose to do so in future.

The pdfsigutil utility doesn't seem to do much. Unless there are plans
to add a lot of extra options and functionality would it be better to
add an option to pdfinfo to check signatures instead of adding a new
util?

-- 
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/1085526

Title:
  ubuntu pdf doc viewer will not let me sign a document

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1085526/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 517021] Re: gvfsd-metadata causes 100% CPU usage

2015-02-02 Thread John Paul Adrian Glaubitz
Are you guys talking about the issue on NFS filesystems or local disks?

There have been two independent issues, the NFS issue was fixed in
around gvfs_1.17 while the other issue was fixed around gvfs_1.22.

NFS issue: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624507
local issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756205

Please make sure to use the latest upstream version of gvfs before
filing any bug reports.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launchpad.net/bugs/517021

Title:
  gvfsd-metadata causes 100% CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/517021/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs


[Bug 116453]

2015-01-13 Thread Adrian Johnson
I'm not sure that removing this functionality is a good idea. Can't we
just add an option to findText to enable a looser search and leave it to
the front ends to decide if/how to expose this option.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/116453

Title:
  evince can not find ü in attached PDF

To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/116453/+subscriptions

-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

  1   2   3   4   >