[Touch-packages] [Bug 1821810] Re: gdebi crashes when trying to install packages
This bug still exists in Ubuntu 22.10. If you open it via the command line (even without sudo/root) it will work and prompt for the password. And if you open it via menu (my .desktop file has `gdebi-gtk %f` as the command) and THEN load the .deb, it will also work. I also tested it on different file managers: Elementary Files (does not work) Nautilus (does not work) Thunar (does not work) Caja (works) Nemo (works) PCMan (works) Rox (works) Thunar in root mode (works) So, seems to be something to do with the way it launches or the way the file is passed to it when it launches maybe? The fact that it doesn't work in Thunar normally but works when Thunar is launched in root mode is strange, don't know if that info helps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1821810 Title: gdebi crashes when trying to install packages Status in gdebi package in Ubuntu: Confirmed Bug description: When I try to install some deb packages gdebi disapears. It does not show me any error report. It will just disapear from my screen. Lubuntu 18.4 LTS gdebi 0.9.5.7+nmu2 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 26 23:30:04 2019 InstallationDate: Installed on 2019-03-18 (8 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1821810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002886] [NEW] Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35
Public bug reported: With GTK 3.24.35, when running under Wayland, it's not possible to copy and paste from Geany. (Others report the same issue with SciTE, which also uses the Scintilla editor.) The Geany upsteam bug isolated the issue to a GTK change (https://github.com/geany/geany/issues/3345#issuecomment-1360370992). The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was resolved (https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd) and the fix is in GTK 3.24.36. I installed the libgtk-3-0_3.24.36-1_amd64.deb and libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test system and this did resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libgtk-3-0 3.24.35-3ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 14:22:01 2023 InstallationDate: Installed on 2022-12-28 (17 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar uec-images wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2002886 Title: Can't copy and paste from Geany (and SciTE?) in Wayland with GTK 3.24.35 Status in gtk+3.0 package in Ubuntu: New Bug description: With GTK 3.24.35, when running under Wayland, it's not possible to copy and paste from Geany. (Others report the same issue with SciTE, which also uses the Scintilla editor.) The Geany upsteam bug isolated the issue to a GTK change (https://github.com/geany/geany/issues/3345#issuecomment-1360370992). The GTK bug (https://gitlab.gnome.org/GNOME/gtk/-/issues/5397) was resolved (https://gitlab.gnome.org/GNOME/gtk/-/commit/eca445672a48ac4a870790efa63339f8d974c2fd) and the fix is in GTK 3.24.36. I installed the libgtk-3-0_3.24.36-1_amd64.deb and libgtk-3-common_3.24.36-1_all.deb packages from Debian on a Lunar test system and this did resolve the issue. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libgtk-3-0 3.24.35-3ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 14 14:22:01 2023 InstallationDate: Installed on 2022-12-28 (17 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2002886/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979281] Re: Maximized window expands behind dock after wakeup from monitor energy powerdown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1979281 Title: Maximized window expands behind dock after wakeup from monitor energy powerdown Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: To reproduce: - maximize a window like the terminal or file manager. - open another window maximized in the foreground. - wait until the energy saving powers down your monitor. - wake the monitor up again The covered, maximized terminal window expanded behind the dock on the left (but not behind the title bar on the top). I'll attach screenshots that are more descriptive than pure text Description: Ubuntu 22.04 LTS Release: 22.04 Session: Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1979281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2
Hi Nafees,
Thank you for the reproducer and instructions.
Per your comments, I would expect this to work well with python3 on
20.04, however, my tests indicated that python2 and python3 are both
behaving the same way. In the example below, I'm using python3 and I
also don't see the -O2 optimization:
ubuntu@ip-172-31-80-78:~/python-bug/testprog-python3-pip$ python3 setup.py
build_ext --inplace
running build_ext
building 'test' extension
creating build/temp.linux-aarch64-3.8
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security
-g -fwrapv -O2 -g -fstack-protector-strong -Wformat -Werror=format-security
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c testmodule.c
-o build/temp.linux-aarch64-3.8/testmodule.o
creating build/lib.linux-aarch64-3.8
aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions
-Wl,-z,relro -g -fwrapv -O2 -g -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
build/temp.linux-aarch64-3.8/testmodule.o -o
build/lib.linux-aarch64-3.8/test.cpython-38-aarch64-linux-gnu.so
copying build/lib.linux-aarch64-3.8/test.cpython-38-aarch64-linux-gnu.so ->
ubuntu@ip-172-31-80-78:~/python-bug/testprog-python3-pip$ strings
test.so | grep -- -O
(output from the command above was empty)
On the other hand, I do see the -O2 with python2 in a 22.04 instance.
Can you clarify if this is the same for you and, if not, provide some
details on versions being used?
Regards,
Fabio Martins
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/2002043
Title:
Python extension modules get built using wrong compiler flags with
python2
Status in python2.7 package in Ubuntu:
New
Bug description:
Compiling a Python extension using Python2 (Python 2.7.18) is making
use of wrong compiler flags, hence dropping required optimizations
when required. This is happening only when python2 is installed from
Ubuntu's repositories. By default, Python's distutils module uses
compiler and linker flags used to compile Python itself to be used to
compile extensions.
Steps to reproduce:
1) On Ubuntu 20.04, install python2 using apt package manager.
2) After successful installation, verify the CFLAGS variable from sysconfig
module. On my machine, the output is
Python 2.7.18 (default, Jul 1 2022, 12:27:04)
[GCC 9.4.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_var('CFLAGS')
'-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-Wdate-time -D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security '
3) Build a test extension module using python2 and verify the compilation
flags.
python2 setup.py build_ext --inplace
Output from below command is not matching with our expected above CFLAGS.
aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time
-D_FORTIFY_SOURCE=2 -g
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC
-I/usr/include/python2.7 -c testmodule.c -o
build/temp.linux-aarch64-2.7/testmodule.o
On further investigation, it looks like Ubuntu's specific patch applied on
libpython2.7-stdlib package is altering the original upstream implementation of
distutils/sysconfig.py code.
Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
Patch -
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
Below is the code block which is causing the issue, where the presence of
configure_cflags is modifying cflags. This code is result of ubuntu's patch and
doesn't come directly from upstream python implementation.
File - /usr/lib/python2.7/distutils/sysconfig.py
Part of code block:
elif configure_cflags:
cflags = ' '.join(str(x) for x in (basecflags, configure_cflags,
extra_cflags) if x)
ldshared = ldshared + ' ' + configure_cflags
I don't see problem on Python3 though we have extra code added from patch
there as well. Patch used on python3, is not modifying the cflags completely
and instead appending new flags to cflags.
On python3 (tested on Ubuntu 20.04)
File - /usr/lib/python3.8/distutils/sysconfig.py
Part of code block which doesn't alter cflags completely
elif configure_cflags:
cflags = cflags + ' ' + configure_cflags
ldshared = ldshared + ' ' + configure_cflags
Request to update the python2 patch to behave similar to what is been done on
python3.
To manage
[Touch-packages] [Bug 905587] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all
Hi! I am still facing this issue. Please guide me here, I am new to
linux environments. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/905587
Title:
[ICH - Intel 82801AA-ICH, playback] No sound at all
Status in alsa-driver package in Ubuntu:
Expired
Bug description:
using rhythmbox on ubuntu 12.04 updated 16-12-2011, trying to play m4a
file no sound. Tried to use sound settings applet, ouput tab, changing
output sound from amplifier to no amplifier caused the crashm
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.24+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-3.9-generic 3.2.0-rc4
Uname: Linux 3.2.0-3-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel
82801AA-ICH]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 1.90-0ubuntu1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bertadmin 17553 F pulseaudio
Card0.Amixer.info:
Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with STAC9700,83,84 at irq 5'
Mixer name : 'SigmaTel STAC9700,83,84'
Components : 'AC97a:83847600'
Controls : 34
Simple ctrls : 24
Date: Fri Dec 16 21:14:31 2011
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386
(20111209.1)
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH
successful
Symptom_Card: Internal Audio - Intel 82801AA-ICH
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
UpgradeStatus: Upgraded to precise on 2011-12-10 (6 days ago)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/905587/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1999098] Re: Update glib to 2.74.3
The autopkgtests all pass now. I installed glib 2.74.3-0ubuntu1, restarted my computer and ensured that epiphany-browser, the file browser and the terminal all appear to work correctly. I also installed gnome-characters 43.1-0ubuntu1 and verified that I was able to search for the moose emoji and copy it. ** Tags removed: verification-needed verification-needed-kinetic ** Tags added: verification-done verification-done-kinetic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1999098 Title: Update glib to 2.74.3 Status in glib2.0 package in Ubuntu: Fix Committed Status in glib2.0 source package in Kinetic: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.74 series The current release in Ubuntu 22.10 is 2.74.0 https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopgktest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser Test Case 3 (Extra) -- Install gnome-characters 43.1. (This is being SRU'd, but the version from Lunar also works.) Open the Characters app. Use the search feature to search for "moose" A moose emoji should show up. This is one of the new Emoji 15. https://blog.emojipedia.org/whats-new-in-unicode-15-0/ With glib 2.74.0, the moose emoji won't be searchable but it does show in the Animals category. What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- Unicode 15 enablement was granted a User Interface Freeze Exception for Ubuntu 22.10: https://launchpad.net/bugs/1989626 glib and gnome-characters are the only 2 late pieces that the Ubuntu Desktop team plans to SRU for Ubuntu 22.10. Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so they are functionally equivalent. Ubuntu 23.04 will get newer glib versions before 23.04 is released. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002869] Re: "ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Thanks for your report!
That kind of issue is really upstream in nature, and nothing we would
like to change in Ubuntu only. So it would be great if you could submit
an upstream issue too:
https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/-/issues
If you do, please add a comment here with the URL.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/2002869
Title:
"ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Status in xkeyboard-config package in Ubuntu:
New
Bug description:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl
modifier key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still
works as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl
as follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl 2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2002869/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2002869] [NEW] "ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Public bug reported:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl modifier
key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still works
as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl as
follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
** Affects: xkeyboard-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/2002869
Title:
"ctrl:swapcaps" doesn't swap shift+capslock and shift+ctrl
Status in xkeyboard-config package in Ubuntu:
New
Bug description:
Ubuntu: 22.10
xkb-data: 2.35.1-1
keyboard layout: jp106
I enable a xkb option "ctrl:swapcaps" and often use shift+ctrl
modifier key combinations like shift+ctrl+T.
Expected:
Both pressing [shift]+[capslock] and [capslock]+[shift] should work as
shift+ctrl modifier.
What happened:
[capslock]+[shift] works as expected, but [shift]+[capslock] still
works as shift+capslock.
This behavior is very confusing and annoying to me.
Workaround:
The problem can be avoided by editing /usr/share/X11/xkb/symbols/ctrl
as follows.
--- ctrl.orig 2022-02-09 02:13:55.0 +0900
+++ ctrl 2023-01-14 18:57:15.589534502 +0900
@@ -14,7 +14,7 @@
// Swap the functions of the CapsLock key and the left Ctrl key.
partial modifier_keys
xkb_symbols "swapcaps" {
-replace key { [ Control_L ] };
+replace key { [ Control_L, Control_L ] };
replace key { [ Caps_Lock ] };
modifier_map Control { };
modifier_map Lock { };
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/2002869/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
