[Touch-packages] [Bug 1877754] Re: GTKFileChooser: deselect highlighted directory
Hi Sebastien, yeah, exactly that was the functionality I looked for - the +click hotkey. Unfortunately it is not very intuitive if you don't know about it. So I guess that I am not the only user which would be more familiar with the click outside... Similar thing about the path editing feature: you may not just click on the breadcrumbs in the top to get the path field as it is the case on other OS as Windows. No, you need to know about the +L shortcut to open it. So put together those are not bugs, but rather usability issues... -- 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/1877754 Title: GTKFileChooser: deselect highlighted directory Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: New Bug description: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him/her-self with no entry highlighted. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1877754/+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 1877754] [NEW] GTKFileChooser: deselect highlighted directory
Public bug reported: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him /her-self with no entry highlighted. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: gtkfilechooser ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Description changed: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted - automatically (when it is not the first time you save a file). So the - user may click on another entry to change the selection, but clicking on - the background *does not cause* a deselection to take place. In my - opinion that would be an expected usage pattern as it is the case on - common other platforms. + automatically which may be a folder (especially when it is not the first + time you save a file). So the user may click on another entry to change + the selection, but clicking on the background *does not cause* a + deselection to take place. In my opinion that would be an expected usage + pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the - working directory and not a particular file. The only valid (and nasty) + current working directory and not a particular folder/file (he doesn't + want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him /her-self with no entry highlighted. -- 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/1877754 Title: GTKFileChooser: deselect highlighted directory Status in Ubuntu: New Bug description: Open a random file save form (gedit, LibreOffice doesn't matter). Sometimes the first entry in the file list gets highlighted automatically which may be a folder (especially when it is not the first time you save a file). So the user may click on another entry to change the selection, but clicking on the background *does not cause* a deselection to take place. In my opinion that would be an expected usage pattern as it is the case on common other platforms. Why is that important? Sometimes the user just needs to choose the current working directory and not a particular folder/file (he doesn't want to have the file stored in a subfolder). The only valid (and nasty) workaround is to go one hierarchy upwards and then double-click the directory folder. The folder gets opened and the user finally finds him/her-self with no entry highlighted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877754/+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 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()
Any news on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1786756] Re: netcat-openbsd broadcast not working
Fixed in Ubuntu 18.04 LTS bionic, so I propose to close this.
** Changed in: netcat-openbsd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1786756
Title:
netcat-openbsd broadcast not working
Status in netcat-openbsd package in Ubuntu:
Fix Released
Bug description:
OS: Ubuntu Xenial Ubuntu 16.04.5 LTS
Package: netcat-openbsd 1.105-7ubuntu1
I want to send broadcasts over the loopback device:
$ nc -vu 127.255.255.255 1024
nc: connect to 127.255.255.255 port 1024 (udp) failed: Permission denied
This does not work since the broadcast socket option hasn't been
enabled which is also correct. So I retry with:
$ nc -vbu 127.255.255.255 1024
nc: Protocol not available
This is strange. Doing an strace reveals the reason:
$ strace nc -u 127.255.255.255 1024
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(3, {sa_family=AF_INET, sin_port=htons(1024),
sin_addr=inet_addr("127.255.255.255")}, 16) = -1 EACCES (Permission denied)
fcntl(3, F_SETFL, O_RDWR) = 0
close(3)= 0
close(-1) = -1 EBADF (Bad file descriptor)
exit_group(1) = ?
+++ exited with 1 +++
Okay, but now with "b":
$ strace nc -bu 127.255.255.255 1024
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
setsockopt(3, SOL_TCP, TCP_KEEPCNT, [1], 4) = -1 ENOPROTOOPT (Protocol not
available)
write(2, "nc: ", 4nc: ) = 4
write(2, "Protocol not available\n", 23Protocol not available
) = 23
exit_group(1) = ?
+++ exited with 1 +++
This is very amazing: why does a TCP socket option get set when I am
requesting the broadcast mode? I have analysed the original Debian package
where the broadcast option gets added (the original OpenBSD package misses it),
but the respective integration patch seems correct to me
(0010-misc-failures-and-features.patch).
Package page: https://packages.debian.org/stretch/netcat-openbsd
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: netcat-openbsd 1.105-7ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Aug 13 11:31:28 2018
Dependencies:
gcc-7-base 7.2.0-8ubuntu3.2 [origin: TUXEDO Computers]
libbsd0 0.8.2-1
libc6 2.23-0ubuntu10
libgcc1 1:7.2.0-8ubuntu3.2 [origin: TUXEDO Computers]
EcryptfsInUse: Yes
SourcePackage: netcat-openbsd
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1786756/+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 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()
Unfortunately I just stumbled over this commit by accident since I checked the commit log of libX11. So for a reproduction we would need to contact the original reporter Sami Farin (https://bugs.freedesktop.org/show_bug.cgi?id=93186) but I do not find any valid email address from him. ** Bug watch added: freedesktop.org Bugzilla #93186 https://bugs.freedesktop.org/show_bug.cgi?id=93186 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1820509] [NEW] Avoid use-after-free in _XimProtoSetIMValues()
Public bug reported: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1820509 Title: Avoid use-after-free in _XimProtoSetIMValues() Status in libx11 package in Ubuntu: New Bug description: I think that the patch https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49) should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04 LTS Bionic. Although it didn't get an explicit CVS, use-after-free scenarios should not get underestimated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1786756] [NEW] netcat-openbsd broadcast not working
Public bug reported:
OS: Ubuntu Xenial Ubuntu 16.04.5 LTS
Package: netcat-openbsd 1.105-7ubuntu1
I want to send broadcasts over the loopback device:
$ nc -vu 127.255.255.255 1024
nc: connect to 127.255.255.255 port 1024 (udp) failed: Permission denied
This does not work since the broadcast socket option hasn't been enabled
which is also correct. So I retry with:
$ nc -vbu 127.255.255.255 1024
nc: Protocol not available
This is strange. Doing an strace reveals the reason:
$ strace nc -u 127.255.255.255 1024
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(3, {sa_family=AF_INET, sin_port=htons(1024),
sin_addr=inet_addr("127.255.255.255")}, 16) = -1 EACCES (Permission denied)
fcntl(3, F_SETFL, O_RDWR) = 0
close(3)= 0
close(-1) = -1 EBADF (Bad file descriptor)
exit_group(1) = ?
+++ exited with 1 +++
Okay, but now with "b":
$ strace nc -bu 127.255.255.255 1024
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
setsockopt(3, SOL_TCP, TCP_KEEPCNT, [1], 4) = -1 ENOPROTOOPT (Protocol not
available)
write(2, "nc: ", 4nc: ) = 4
write(2, "Protocol not available\n", 23Protocol not available
) = 23
exit_group(1) = ?
+++ exited with 1 +++
This is very amazing: why does a TCP socket option get set when I am requesting
the broadcast mode? I have analysed the original Debian package where the
broadcast option gets added (the original OpenBSD package misses it), but the
respective integration patch seems correct to me
(0010-misc-failures-and-features.patch).
Package page: https://packages.debian.org/stretch/netcat-openbsd
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: netcat-openbsd 1.105-7ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Aug 13 11:31:28 2018
Dependencies:
gcc-7-base 7.2.0-8ubuntu3.2 [origin: TUXEDO Computers]
libbsd0 0.8.2-1
libc6 2.23-0ubuntu10
libgcc1 1:7.2.0-8ubuntu3.2 [origin: TUXEDO Computers]
EcryptfsInUse: Yes
SourcePackage: netcat-openbsd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: netcat-openbsd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages xenial
** Description changed:
OS: Ubuntu Xenial Ubuntu 16.04.5 LTS
Package: netcat-openbsd 1.105-7ubuntu1
I want to send broadcasts over the loopback device:
$ nc -vu 127.255.255.255 1024
nc: connect to 127.255.255.255 port 1024 (udp) failed: Permission denied
This does not work since the broadcast socket option hasn't been enabled
which is also correct. So I retry with:
$ nc -vbu 127.255.255.255 1024
nc: Protocol not available
This is strange. Doing an strace reveals the reason:
$ strace nc -u 127.255.255.255 1024
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
fcntl(3, F_GETFL) = 0x2 (flags O_RDWR)
fcntl(3, F_SETFL, O_RDWR|O_NONBLOCK)= 0
connect(3, {sa_family=AF_INET, sin_port=htons(1024),
sin_addr=inet_addr("127.255.255.255")}, 16) = -1 EACCES (Permission denied)
fcntl(3, F_SETFL, O_RDWR) = 0
close(3)= 0
close(-1) = -1 EBADF (Bad file descriptor)
exit_group(1) = ?
+++ exited with 1 +++
Okay, but now with "b":
$ strace nc -bu 127.255.255.255 1024
...
socket(PF_INET, SOCK_DGRAM, IPPROTO_UDP) = 3
setsockopt(3, SOL_TCP, TCP_KEEPCNT, [1], 4) = -1 ENOPROTOOPT (Protocol not
available)
write(2, "nc: ", 4nc: ) = 4
write(2, "Protocol not available\n", 23Protocol not available
) = 23
exit_group(1) = ?
+++ exited with 1 +++
- This is very amazing: why does a TCP socket option get set when I am
- requesting the broadcast mode? I have analysed the original Debian
- package where the broadcast option gets added (in the original OpenBSD
- package it is not existing), but the respective integration patch seems
- correct to me (0010-misc-failures-and-features.patch). Package page:
- https://packages.debian.org/stretch/netcat-openbsd
+ This is very amazing: why does a TCP socket option get set when I am
requesting the broadcast mode? I have analysed the original Debian package
where the broadcast option gets added (the original OpenBSD package misses it),
but the respective integration patch seems correct to me
(0010-misc-failures-and-features.patch).
+ Package page: https://packages.debian.org/stretch/netcat-openbsd
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: netcat-openbsd 1.105-7ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18
Uname:
