Re: [Bug 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

2020-05-08 Thread Wolf Pichler
It should indeed be done like this:

 import gi
 gi.require_version('Gtk', '3.0')
 from gi.repository import Gtk

 from gi.repository import GObject

 mystore = Gtk.ListStore(GObject.TYPE_UINT64)
 mystore.insert_with_valuesv(-1, [1], [GObject.Value(GObject.TYPE_UINT64, 
1330400507426)])

###

I was completely unaware of that possibility because the source of my
GTK knowlege is

https://lazka.github.io/pgi-
docs/#Gtk-3.0/classes/ListStore.html#Gtk.ListStore.set_column_types

When checking out the available types one ends up here:

https://lazka.github.io/pgi-
docs/#GObject-2.0/classes/GType.html#GObject.GType

Which does not ring any bell ...

So I did it like in

https://python-gtk-3-tutorial.readthedocs.io/en/latest/treeview.html
#the-model

where the Python types are used.

###

With the knowlege I gained through this FR it was possible to find this:

GObject Built-in Type Constants
The Built-in Type constants specify the pre-defined types used by gobject.

https://developer.gnome.org/pygobject/stable/gobject-constants.html
#gobject-type-constants

which is quite useful.

###

Thanks!

On 11.03.20 17:56, Christoph Reiter wrote:
>  import gi
>   gi.require_version('Gtk', '3.0')
>   from gi.repository import Gtk
>
>   This works in Python 2:
>
>   mystore = Gtk.ListStore(long)
>   mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])
>
>   This does not work in Python 3:
>
>   mystore = Gtk.ListStore(int)
>   mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

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

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

Re: [Bug 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

2020-03-09 Thread Wolf Pichler
It works!

On 09.03.20 21:17, Sebastien Bacher wrote:
> COuld you test the upstream workaround and use
> GObject.Value(GObject.TYPE_UINT64, 1330400507426) ?
>

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

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

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

Re: [Bug 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

2020-03-09 Thread Wolf Pichler
I'm not sure what exactly they are really talking about at
https://gitlab.gnome.org/GNOME/pygobject/issues/198.

My FR concerns 3.26.1-2ubuntu1 and at gitlab it is stated "I think it
used to work in 3.26." which

clearly is not the case.


I took a look into the source and in pygi-value.c I found this:

case G_TYPE_INT:
    {
    glong val = PYGLIB_PyLong_AsLong(obj);
    if (val == -1 && PyErr_Occurred ())
    return -1;
    if (val > G_MAXINT || val < G_MININT) {
    PyErr_SetString(PyExc_OverflowError, "out of range for int
property");
    return -1;
    }
    g_value_set_int(value, (gint)val);
    break;
    }


and a lot of comments like this:


#if PY_VERSION_HEX < 0x0300

[snip]

#endif


To me this means that somebody is/was aware of the fact that some more
work has to be done for

making this stuff compatible to Python 3.


On 09.03.20 14:48, Sebastien Bacher wrote:
> Thank you for your bug report, that seems similar to
> https://gitlab.gnome.org/GNOME/pygobject/issues/198
>
> ** Bug watch added: gitlab.gnome.org/GNOME/pygobject/issues #198
>https://gitlab.gnome.org/GNOME/pygobject/issues/198
>
> ** Changed in: pygobject (Ubuntu)
>Importance: Undecided => Low
>

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

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

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

[Bug 1866625] [NEW] OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

2020-03-09 Thread Wolf Pichler
Public bug reported:

import gi
gi.require_version('Gtk', '3.0')
from gi.repository import Gtk

This works in Python 2:

mystore = Gtk.ListStore(long)
mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])

This does not work in Python 3:

mystore = Gtk.ListStore(int)
mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

OverflowError: Item 0: out of range for int property



lsb_release -rd
Description:Ubuntu 18.04.4 LTS
Release:18.04

apt-cache policy python3-gi
python3-gi:
  Installed: 3.26.1-2ubuntu1
  Candidate: 3.26.1-2ubuntu1
  Version table:
 *** 3.26.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.26.1-2 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

python3 -V
Python 3.6.9

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

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

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

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

Re: [Bug 1841051] Re: gpg password cache is never cleared

2019-11-05 Thread Wolf Pichler
Thanks!

On 05.11.19 21:30, Sebastien Bacher wrote:
> thanks, closing then
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: Incomplete => Invalid
>

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

Title:
  gpg password cache is never cleared

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

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

Re: [Bug 1841051] Re: gpg password cache is never cleared

2019-11-05 Thread Wolf Pichler
It is no fault.

My original FR concerned gpg-agent because I was unaware of the fact
that

seahorse/gnome-keyring had the password stored.

On 05.11.19 11:26, Sebastien Bacher wrote:
> Thank you for your bug report. Could you give details on what you did
> exactly? If you ticked the box to store the auth in the keyring that's
> what it did, why would you expect it to do instead?
>
> ** Package changed: seahorse (Ubuntu) => gnome-keyring (Ubuntu)
>
> ** Changed in: gnome-keyring (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  gpg password cache is never cleared

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

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

[Bug 1791054] Re: Ubuntu 18.04.1 becomes unresponsive after Logout or Resume

2018-09-10 Thread Wolf Pichler
Done.

cat /var/lib/whoopsie/whoopsie-id
9308e09d7878d0c0d8ead53939cd5e88e7c149ecd35cb08a25e4baa94126f02dc10b574f67e99c30cfae4f2ee05852ce672611907b1c0d49afa3bf0a48bd

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

Title:
  Ubuntu 18.04.1 becomes unresponsive after Logout or Resume

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

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

[Bug 1791054] Re: Ubuntu 18.04.1 becomes unresponsive after Logout or Resume

2018-09-07 Thread Wolf Pichler
For a while Logout/Resume/Switch User worked fine with Wayland (as well
as with Xorg when I cross-checked it).

But finally, when I tried "Switch User" again with Wayland, I got stuck
on the Login-Page of the current user - it was not possible to get the
page displaying all available users.

To be sure I made no mistake I checked:
echo $XDG_SESSION_TYPE
wayland

The first line in the attached syslog should be the moment when I clicked 
"Switch User".
The last line seems to be the moment when I logged in as original user again.
Both lines contain the same error message.


** Attachment added: "syslog_Wayland_UserSwitch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1791054/+attachment/5186149/+files/syslog_Wayland_UserSwitch

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

Title:
  Ubuntu 18.04.1 becomes unresponsive after Logout or Resume

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

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

[Bug 1791054] [NEW] Ubuntu 18.04.1 becomes unresponsive after Logout or Resume

2018-09-06 Thread Wolf Pichler
Public bug reported:

After Logout or Resume one ultimately ends up at a black screen on a
completely unresponsive system.

Only the power button helps in this case - I guess the "Emergency Sync"
in the attached syslog marks the point in time when the power button was
pressed.

###

apt-cache policy gdm3:
gdm3:
  Installed: 3.28.2-0ubuntu1.4
  Candidate: 3.28.2-0ubuntu1.4
  Version table:
 *** 3.28.2-0ubuntu1.4 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
 3.28.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

lsb_release -rd:
Description: Ubuntu 18.04.1 LTS
Release: 18.04

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


** Tags: bionic

** Attachment added: "syslog_unresponsive"
   
https://bugs.launchpad.net/bugs/1791054/+attachment/5185549/+files/syslog_unresponsive

** Package changed: system-config-printer (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  Ubuntu 18.04.1 becomes unresponsive after Logout or Resume

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

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