[Touch-packages] [Bug 1864215] Re: Please add webp loader to gdk-pixbuf

2021-05-02 Thread Dark Dragon
** Bug watch added: Debian Bug tracker #951113 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951113 ** Also affects: debian via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951113 Importance: Unknown Status: Unknown -- You received this bug notification because you are a

[Touch-packages] [Bug 1886272] Re: Request to package webp pixbuf

2021-05-02 Thread Dark Dragon
*** This bug is a duplicate of bug 1864215 *** https://bugs.launchpad.net/bugs/1864215 ** This bug has been marked a duplicate of bug 1864215 Please add webp loader to gdk-pixbuf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subsc

[Touch-packages] [Bug 1905768] Re: ld: DWARF error: could not find variable specification at offset

2020-11-29 Thread Dark Dragon
I can confirm that the version available in hirsute fixes the problem. Please backport it also to groovy. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1905768 Title: ld

[Touch-packages] [Bug 1905768] Re: ld: DWARF error: could not find variable specification at offset

2020-11-26 Thread Dark Dragon
Will this be backported to groovy? I can't build my software any more. Working as a software developer this is a big problem! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/

[Touch-packages] [Bug 1905768] [NEW] ld: DWARF error: could not find variable specification at offset

2020-11-26 Thread Dark Dragon
Public bug reported: Fixed upstream. Please update (I still get the error in 2.35.1-1ubuntu1 on groovy). ** Affects: binutils (Ubuntu) Importance: Undecided Status: New ** Affects: binutils (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug t

[Touch-packages] [Bug 1864280] Re: software-properties-gtk removes [arch=amd64]

2020-07-02 Thread Dark Dragon
** Changed in: software-properties (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864280 Title: software-properti

[Touch-packages] [Bug 1864280] Re: software-properties-gtk removes [arch=amd64]

2020-06-27 Thread Dark Dragon
Can someone please reopen this? I provided the necessary details for producibility... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1864280 Title: software-pr

[Touch-packages] [Bug 1876518] Re: Gtk.Clipboard set_text() not working

2020-05-04 Thread Dark Dragon
** Bug watch added: gitlab.gnome.org/GNOME/pygobject/-/issues #405 https://gitlab.gnome.org/GNOME/pygobject/-/issues/405 ** Also affects: pygobject via https://gitlab.gnome.org/GNOME/pygobject/-/issues/405 Importance: Unknown Status: Unknown -- You received this bug notification

[Touch-packages] [Bug 1876518] [NEW] Gtk.Clipboard set_text() not working

2020-05-02 Thread Dark Dragon
Public bug reported: Writing to Gtk.Clipboard doesn't work (reading works). Example code: #!/usr/bin/python3 import gi gi.require_version('Gtk', '3.0') from gi.repository import Gtk, Gdk clipboard = Gtk.Clipboard.get(Gdk.SELECTION_CLIPBOARD) clipboard.set_text("Does a text of all texts contain i

[Touch-packages] [Bug 1864280] Re: software-properties-gtk removes [arch=amd64]

2020-04-27 Thread Dark Dragon
Create via $ echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable" > /etc/apt/sources.list.d/docker.list Distribution upgrade disables all third-party sources and adds a comment. When I use software-properties-gtk to remove the comment, the "[arch=amd64]" addition is no lo

[Touch-packages] [Bug 1864280] [NEW] software-properties-gtk removes [arch=amd64]

2020-02-21 Thread Dark Dragon
Public bug reported: When editing apt sources via software-properties-gtk, additional options like [arch=amd64] are removed. With more and more repositories deprecating i386, this problem becomes more and more important. ** Affects: software-properties (Ubuntu) Importance: Undecided

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2019-10-02 Thread Dark Dragon
Thanks a lot! I will investigate ways to correct this information: https://github.com/linuxhw/EDID/issues/4 ** Bug watch added: github.com/linuxhw/EDID/issues #4 https://github.com/linuxhw/EDID/issues/4 -- You received this bug notification because you are a member of Ubuntu Touch seeded pack

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2019-09-30 Thread Dark Dragon
How can I check if the hardware is really sending faulty data or if it is just incorrectly parsed? ** Also affects: xrandr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to q

[Touch-packages] [Bug 1825380] [NEW] Add field architecture for "Other Software" entries

2019-04-18 Thread Dark Dragon
Public bug reported: Nowadays, many packages only offer amd64 versions and no i386 version (attribute [arch=amd64]). There is no way to specify this in software- properties-gtk! ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug not

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-20 Thread Dark Dragon
Do you need any additional information? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1792167 Title: Display size detected incorrectly Status in mutter pac

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-14 Thread Dark Dragon
I booted up a live disk with Ubuntu 17.04 (Unity) and it shows the same behavior. ** Description changed: - Since Ubuntu switched to Gnome, display scaling does not work correctly. - This is because my external monitor is detected as 7" although it is - 32". All applications which use Qt auto sca

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-14 Thread Dark Dragon
Same result when I connect via DP->HDMI adapter ** Attachment added: "xrandr output for external display on adapter" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+attachment/5188740/+files/xrandr.log -- You received this bug notification because you are a member of Ubuntu To

[Touch-packages] [Bug 1792167] ProcCpuinfoMinimal.txt

2018-09-13 Thread Dark Dragon
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1792167/+attachment/5188325/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-

[Touch-packages] [Bug 1792167] ProcEnviron.txt

2018-09-13 Thread Dark Dragon
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1792167/+attachment/5188326/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu.

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-13 Thread Dark Dragon
apport information ** Tags added: apport-collected bionic ** Description changed: Since Ubuntu switched to Gnome, display scaling does not work correctly. This is because my external monitor is detected as 7" although it is 32". All applications which use Qt auto scaling have huge controls

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

2018-09-13 Thread Dark Dragon
1. xrandr I generated the output and attached the section for the external display. I guess the first line already shows the problem: HDMI-1 connected 1920x1080+1366+0 (0x8b) normal (normal left inverted right x axis y axis) 160mm x 90mm It includes "160mm x 90mm" which probably translates t

[Touch-packages] [Bug 1792167] Re: Display size detected wrongly

2018-09-12 Thread Dark Dragon
** Also affects: kernel Importance: Undecided Status: New ** Also affects: xorg-server Importance: Undecided Status: New ** Summary changed: - Display size detected wrongly + Display size detected incorrectly -- You received this bug notification because you are a member of