Bug#961604: History was empty on first startup, but appeared on second launch

2020-05-26 Thread Oliver Sauder
This is a known issue see https://bugs.launchpad.net/diodon/+bug/1435033

Unfortunately so far it is not quite clear what causes this. Any
comments are welcome.

Oliver

On 26.05.20 16:58, Christoph Berg wrote:
> Package: diodon
> Version: 1.9.0-1
> Severity: normal
> 
> Hi,
> 
> I just started using diodon because clipit notified me that it is
> gone.
> 
> On the first startup, I selected some options (notably to track the
> primary selection and to sync selections), and tried to select some
> things. The history in the diodon systray icon remained empty
> ("").
> 
> Upon killing diodon and restarting it, things started working.
> 
> Using awesome, no gnome or other DE.
> 
> $ diodon
> 
> (diodon:29053): dbind-WARNING **: 16:58:18.339: Couldn't connect to 
> accessibility bus: Failed to connect to socket /tmp/dbus-Dz5rIZiGzD: 
> Verbindungsaufbau abgelehnt
> 
> (diodon:29053): Gdk-CRITICAL **: 16:58:18.535: 
> gdk_window_thaw_toplevel_updates: assertion 
> 'window->update_and_descendants_freeze_count > 0' failed
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing
>   APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
> Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
> LANGUAGE=de:en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages diodon depends on:
> ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
> ii  libappindicator3-1   0.4.92-8
> ii  libc62.30-8
> ii  libdiodon0   1.9.0-1
> ii  libglib2.0-0 2.64.2-1
> ii  libgtk-3-0   3.24.20-1
> ii  libpeas-1.0-01.26.0-2
> ii  zeitgeist-core   1.0.2-3
> 
> diodon recommends no packages.
> 
> diodon suggests no packages.
> 
> -- no debconf information
> 
> Christoph
> 



Bug#961604: History was empty on first startup, but appeared on second launch

2020-05-26 Thread Christoph Berg
Package: diodon
Version: 1.9.0-1
Severity: normal

Hi,

I just started using diodon because clipit notified me that it is
gone.

On the first startup, I selected some options (notably to track the
primary selection and to sync selections), and tried to select some
things. The history in the diodon systray icon remained empty
("").

Upon killing diodon and restarting it, things started working.

Using awesome, no gnome or other DE.

$ diodon

(diodon:29053): dbind-WARNING **: 16:58:18.339: Couldn't connect to 
accessibility bus: Failed to connect to socket /tmp/dbus-Dz5rIZiGzD: 
Verbindungsaufbau abgelehnt

(diodon:29053): Gdk-CRITICAL **: 16:58:18.535: 
gdk_window_thaw_toplevel_updates: assertion 
'window->update_and_descendants_freeze_count > 0' failed


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de:en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages diodon depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.36.0-1
ii  libappindicator3-1   0.4.92-8
ii  libc62.30-8
ii  libdiodon0   1.9.0-1
ii  libglib2.0-0 2.64.2-1
ii  libgtk-3-0   3.24.20-1
ii  libpeas-1.0-01.26.0-2
ii  zeitgeist-core   1.0.2-3

diodon recommends no packages.

diodon suggests no packages.

-- no debconf information

Christoph