[Bug 1909699] [NEW] Please upgrate to Meld 3.21 for Hirsute Hippo
Public bug reported: Meld 3.21 integrates better with the recent versions of Ubuntu. Please consider upgrading the deb package to version 3.21.x for Hirsute Hippo. References: https://askubuntu.com/a/1302505/100356 https://github.com/GNOME/meld ** Affects: meld (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot of Meld 3.21.1" https://bugs.launchpad.net/bugs/1909699/+attachment/5448113/+files/Screenshot%20from%202020-12-30%2018-20-55.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909699 Title: Please upgrate to Meld 3.21 for Hirsute Hippo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/meld/+bug/1909699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880277] Re: Ubiquity crashes on while installing Ubuntu 20.04
*** This bug is a duplicate of bug 1880344 *** https://bugs.launchpad.net/bugs/1880344 ** This bug has been marked a duplicate of bug 1880344 Cubic Experimental - Ubiquity crashes during installation of a customized ISO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880277 Title: Ubiquity crashes on while installing Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880263] Re: Ubiquity consistently crashes in Ubuntu 20.04
*** This bug is a duplicate of bug 1880344 *** https://bugs.launchpad.net/bugs/1880344 ** This bug has been marked a duplicate of bug 1880344 Cubic Experimental - Ubiquity crashes during installation of a customized ISO -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880263 Title: Ubiquity consistently crashes in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880277] [NEW] Ubiquity crashes on while installing Ubuntu 20.04
Public bug reported: Ubiquity crashes on while installing Ubuntu 20.04 Options selected: ~ Normal install ~ Do not download updates ~ Something else ~ Selected install partition, efi partition, and mount points for two additional partitions ~ All partitions were ext4 (except efi partition) Ubiquity crashed when the install was almost complete. Ubiquity displayed "Configuring apt" expander. The following output was visible on the terminal window below the expander: May 23 02:08:10 ubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 1 May 23 02:08:10 ubuntu /plugininstall.py /usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:17: Warning: Source ID 8302 was not found when attempting to remove it GLib.source_remove(self.timeout_id) /usr/lib/ubiquity/ubiquity/frontend/gtk_components/nmwidgets.py:133: Warning: Source ID 8475 was not found when attempting to remove it GLib.source_remove(self.rows_changed_id) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Sat May 23 02:09:41 2020 InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/ubuntu.iso noprompt noeject LiveMediaBuild: Ubuntu 20.04.0 2020.05.23 LTS "Custom Focal Fossa" (20200523) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880277 Title: Ubiquity crashes on while installing Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880263] Re: Ubiquity consistently crashes in Ubuntu 20.04
When I try to re-run ubiquity, I get the error, ubi-partman failed with exit code 10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880263 Title: Ubiquity consistently crashes in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880263] Re: Ubiquity consistently crashes in Ubuntu 20.04
Ubiquity crashes when installation is almost finished. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880263 Title: Ubiquity consistently crashes in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880263] [NEW] Ubiquity consistently crashes in Ubuntu 20.04
Public bug reported: It's not clear what the bug or issue is. Attempting to install Ubuntu 20.04 on HP Spectre. The only message I see on the command line is... $ ubiquity /usr/bin/ubiquity:74: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Fri May 22 23:23:08 2020 InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper acpi=off iso-scan/filename=/ubuntu.iso noprompt noeject LiveMediaBuild: Ubuntu 20.04.0 2020.05.23 LTS "Custom Focal Fossa" (20200522) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880263 Title: Ubiquity consistently crashes in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1880263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
I did additional testing, and I can confirm that adding "rmmod tpm" does
indeed work...
See comment number 51 by Alkis
(https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/comments/51).
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
menuentry "Install" {
set isofile="/ubuntu.iso"
rmmod tpm
loopback loop (hd0,2)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile
noprompt noeject
initrd (loop)/casper/initrd
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
The Busy Box error I had experienced was actually due to a bad ISO file.
I tested "rmmod tpm" on a system running Ubuntu 19.10.
I tested two official Ubuntu *.iso files:
- Ubuntu 18.04
- Ubuntu 20.04
In both cases, the system successfully booted the specified *.iso.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
@Alkis Georgopoulos,
Thanks for the suggestion.
I added "rmmod tpm".
Unfortunately, it did not really help my situation...
$ sudo update-grub
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.0-51-generic
Found initrd image: /boot/initrd.img-5.3.0-51-generic
Found linux image: /boot/vmlinuz-5.3.0-46-generic
Found initrd image: /boot/initrd.img-5.3.0-46-generic
Adding boot menu entry for EFI firmware configuration
done
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
$ sudo nano /etc/grub.d/40_custom
$ sudo update-grub
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.3.0-51-generic
Found initrd image: /boot/initrd.img-5.3.0-51-generic
Found linux image: /boot/vmlinuz-5.3.0-46-generic
Found initrd image: /boot/initrd.img-5.3.0-46-generic
Adding boot menu entry for EFI firmware configuration
done
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
$ cat /etc/grub.d/40_custom
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type
the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "Install" {
set isofile="/ubuntu.iso"
rmmod tpm
loopback loop (hd0,2)$isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile
noprompt noeject
initrd (loop)/casper/initrd
}
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Prior to this change, I would get a blank screen with a whirring fan.
With the above change, I do see the boot-up log messages.
But, I get a busy box...
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
BusyBox v1.301 (Ubuntu 1:1.30.1-4ubuntu4) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs) Begin: Running /scripts/casper-premount ... done.
Begin: waiting for devs... ... done.
touch /dev/.initramfs/lupin-waited-for-devs: No such file or directory
stdin: Invalid argument
done.
loop: can't get info on device /dev/loop1: No such device or address
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
I don't know why it is referencing "loop1" ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666]
I'm using 3.34.1 in Ubuntu 19.10, and I don't experience this issue anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723678] Re: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard.
James, Per comment #5 (https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/1723678/comments/5) you should probably open a new bug report, and link this old bug. (Also, add a comment here with the link to the new bug report, so folks that are subscribed to this bug and are also still experiencing this issue can indicate that they are impacted). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
* Ximin, apologies for the misspelling of your name; the spellcheck override what I had typed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
Coming, This is good research. Thanks for testing. Perhaps the cause is a secondary library or dependency that iso9660.mod is using? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
Does anyone know which package contains the iso9660 module for grub? Would it be possible to copy the iso9660 module from the the 19.04 or 18.04 Ubuntu releases (e.g. grub 2.02), and explicitly load it before executing the loopback command? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
I can confirm that Booting ISO files from BIOS in Ubuntu 19.10 works fine. UEFI seems to have the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
During bootup, I enter the grub2 command-line by pressing c on the Grub menu. When I type the following command... loopback loop (hd0,gpt2)/ubuntu-19.10-desktop-amd64.iso ...grub hangs, there is no more output or activity on the terminal, and eventually the laptop fans spin up because the laptop gets hot. The path (hd0,gpt2)/ubuntu-19.10-desktop-amd64.iso is valid on my system. I am experiencing this in Ubuntu 19.10 and did not have this issue in prior Ubuntu releases. The version of grub2 and grub2-common I have is 2.04-1ubuntu12. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I am using 18.10 and I have not yet experienced this issue. For me, in 18.04, something that consistently triggered this bug was whenever I accidentally touched the touch-screen on my laptop while adjusting it. In 19.04, I am able to interact with the touch-screen using my fingers, and this issue has not appeared yet. Also, I never used workspace related extensions. So, it is possible that there are multiple issues here, that all have the same symptom. Perhaps there is a common underlying cause, such as a memory issue, as Daniel van Vugt had suggested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825919] Re: Gedit right click context menu stops working
It just happened now... When this happened, I had right clicked on a misspelled work in a Firefox text area. I didn't get a popup context menu; I thought it was just Firefox acting up. So, I switched to my open Gedit window, to cut the correctly spelled word from my text document, and the context menu in Gedit wouldn't work either. It didn't work for a while. But as I started to research and copy logs in order to collect information to post here, the right click context menu magically started to work again, after some time. I'll post the journalctl out put here. The issue happened around 10:19 in the logs... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825919 Title: Gedit right click context menu stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825919] Re: Gedit right click context menu stops working
Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded. Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Logs' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="u Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.clocks' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.clocks' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Characters.BackgroundService' Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Calculator.SearchProvider' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: M Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 systemd[1]: Starting Snappy daemon... Apr 25 10:19:21 PS006 snapd[1036]: AppArmor status: apparmor is enabled and all features are available Apr 25 10:19:21 PS006 snapd[1036]: daemon.go:379: started snapd/2.38+19.04 (series 16; classic) ubuntu/19.04 (amd64) linux/5.0.0-13-generic. Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 systemd[1]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1745]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1217]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1]: Started Snappy daemon. Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMet Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:21 PS006
[Bug 1825919] Re: Gedit right click context menu stops working
NON_DEFAULT EXTENSIONS -- Dash to Dock https://extensions.gnome.org/extension/307/dash-to-dock/ Note: I have removed gnome-shell-extension-ubuntu-dock Bluetooth Quick Connect https://extensions.gnome.org/extension/1401/bluetooth-quick-connect/ Caffeine [INACTIVE] https://extensions.gnome.org/extension/517/caffeine/ Clipboard Indicator https://extensions.gnome.org/extension/779/clipboard-indicator/ Coverflow Alt-Tab https://extensions.gnome.org/extension/97/coverflow-alt-tab/ Printers https://extensions.gnome.org/extension/1218/printers/ Refresh Wifi Connections https://extensions.gnome.org/extension/905/refresh-wifi-connections/ Sound Input & Output Device Chooser https://extensions.gnome.org/extension/906/sound-output-device-chooser/ TLP Switcher https://extensions.gnome.org/extension/1212/tlp-switcher/ DEFAULT EXTENSIONS -- Desktop Icons [INACTIVE] Note: Default Ubuntu extension Ubuntu appindicators Note: Default Ubuntu extension GEDIT PLUGINS - I have the following Gedit plugin packages installed: 1. gedit-plugins 2. gedit-source-code-browser-plugin The following Gedit plugins are activated: Character Map Code Comment Document Statistics File Browser Panel Find in Files Insert Date/Time Join/Split Lines Smart Spaces Sort Source Code Browser Spell Checker Word Completion Zeitgeist dataprovider REPRODUCING ISSUE - I haven't been able to find a consistent way to reproduce this issue... It occurs after using Gedit for a long time. I use Gedit heavily, open many tabs, and open local and remote text documents. I do lot of cut-and-paste, I use the right-click context menu a frequently to cut or paste text. While using Gedit, I simultaneously use Meld, and sometimes I have the same document(s) open in Gedit and in Meld. I may edit a document at the same time in Meld and in Gedit. (When I do this, I simply reload the file when Meld or Gedit warn me that a file has changed). One extension that I use heavily is Clipboard Indicator. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825919 Title: Gedit right click context menu stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825919] Re: Right click context menu stops working
I see this in my application logs: Unable to parse accelerator ???:ignored request to install 6 accelerators (Where ??? is a non-printing character). ** Description changed: The Gedit text area right-click context menu stops appearing. - This bug affects Ubuntu 19.10, but may be a regression of old Bug + This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. ** Summary changed: - Right click context menu stops working + Gedit right click context menu stops working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825919 Title: Gedit right click context menu stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Still present in Ubuntu 19.04, fresh install. (Although, now, clicking twice seems to bring up the authentication dialog, and you don't have to click very rapidly). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Ubuntu version 19.04 GTK3 version 3.24.8-1ubuntu1 Gnome Shell Version 3.32.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825919] [NEW] Right click context menu stops working
Public bug reported: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.10, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Description changed: The Gedit text area right-click context menu stops appearing. - This may be a regression of old Bug #1731581 from Ubuntu 17.10. + This bug affects Ubuntu 19.10, but may be a regression of old Bug + #1731581 from Ubuntu 17.10. - Gedit version: 3.32.0-3 - Fresh install of Ubuntu 19.04 - gkt-3 version: 3.24.8-1ubuntu1 + Gedit version: 3.32.0-3 + Fresh install of Ubuntu 19.04 + gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825919 Title: Right click context menu stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
For reference, here are the upstream bugs: GITLAB: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 BUGZILLA: https://bugzilla.gnome.org/show_bug.cgi?id=724935 https://bugzilla.gnome.org/show_bug.cgi?id=703046 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738676 Title: With natural scrolling, horizontal sliders behave backwards To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
This bug is still being tracked in bugzilla. ** Bug watch added: GNOME Bug Tracker #724935 https://gitlab.gnome.org/724935 ** Changed in: gnome-shell Status: New => Unknown ** Changed in: gnome-shell Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1159 => GNOME Bug Tracker #724935 ** Bug watch added: GNOME Bug Tracker #703046 https://gitlab.gnome.org/703046 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738676 Title: With natural scrolling, horizontal sliders behave backwards To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Oops, I meant to say, "Less than *4* doesn't work, and more than 4 are not necessary." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards
I opened this issue against gnome-shell, upstream. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 I did not report this bug against gtk+3.0. Should I do that as well? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1159 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/1159 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738676 Title: With natural scrolling, horizontal sliders behave backwards To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740894] Re: KEY_RFKILL is not passed to userspace
Works on 18.10 x64 for me... $ sudo apt update $ sudo apt install --reinstall libxkbcommon0 libxkbcommon-x11-0 xkb-data Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Interesting... I tried that, and I noticed that 4 rapid clicks (actually taps on my touchpad) consistently brings up the pkexec password box. Less than 3 doesn't work, and more than 4 are not necessary. Once you've been authenticated, you are able to make changes on the Other Software tab, as you would expect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
Sam James Houlbrook, If you are still having this problem, after updating, you'll need to open a new bug report, since a fix was released. (I am able to type capital enters using the onscreen keyboard in 18.10, so I can't test this in 18.04). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1730211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
Marco, I tried the extension level patch at https://github.com/micheleg/dash- to-dock/issues/128#issuecomment-432913072. Here are my findings... #1 It worked great for preventing two instances of am application from launching when touching an icon on the dock. #2 However, touching the App Grid Icon still does not work. (It seems like the App Grid is unresponsive, but what is really happening is that the applications overview appears briefly and suddenly disappears, as if you had tapped on the App grid Icon twice). Does the fix at https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/272 resolve item #2 above? System Info... $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.10 Release:18.10 Codename: cosmic $ gnome-shell --version GNOME Shell 3.30.1 $ uname -r 4.18.0-10-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745888 Title: Two instances of a program launch whenever you touch a favorites icon To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
I'm willing to help test this, so please let me know what to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745888 Title: Two instances of a program launch whenever you touch a favorites icon To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1745888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
The fact that the Dash is visible on the desktop ~immediately after~ a touch event seems to be contributing to the problem. See this experiment I did... https://github.com/micheleg/dash-to- dock/issues/128#issuecomment-423012581 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Reading through the bug report linked by Daniel van Vugt (vanvugt) in comment #24 (https://github.com/micheleg/dash-to-dock/issues/128), I noticed that Dash-to-Dock is only affected. I had uninstalled the Ubuntu Dock... $ sudo apt autoremove --purge gnome-shell-extension-ubuntu-dock However, I was using the Dash-to-Dock extension, instead. $ sudo apt install gnome-shell-extension-dashtodock So, I disabled Dash-to-Dock. Now the problem is gone. Are all of you using either Dash-to-Dock or the Ubuntu-Dock? If so, what happens when you disable or remove it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
I'll go first... $ sudo dmidecode | grep -A9 "System Information" System Information Manufacturer: HP Product Name: HP Spectre x360 Convertible 15-bl1XX Version: Serial Number: 5CD74284QL UUID: 37444335-3234-3438-514C-4C3432344435 Wake-up Type: Power Switch SKU Number: 1VW22AV Family: 103C_5335KV HP Spectre $ sudo lshw -short H/W path Device Class Description = system HP Spectre x360 Convertible 15-bl1XX (1VW22AV) /0 bus827F /0/0 memory 64KiB BIOS /0/10 memory 16GiB System Memory /0/10/0memory 8GiB SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2667 MHz (0.4 ns) /0/10/1memory 8GiB SODIMM DDR4 Synchronous Unbuffered (Unregistered) 2667 MHz (0.4 ns) /0/14 memory 256KiB L1 cache /0/15 memory 1MiB L2 cache /0/16 memory 8MiB L3 cache /0/17 processor Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz /0/100 bridge Intel Corporation /0/100/2 displayIntel Corporation /0/100/4 genericSkylake Processor Thermal Subsystem /0/100/13 genericIntel Corporation /0/100/14 busSunrise Point-LP USB 3.0 xHCI Controller /0/100/14/0usb1busxHCI Host Controller /0/100/14/0/5 multimedia HP TrueVision FHD RGB-IR /0/100/14/0/7 communication Bluetooth wireless interface /0/100/14/1usb2busxHCI Host Controller /0/100/14.2genericSunrise Point-LP Thermal subsystem /0/100/15 genericSunrise Point-LP Serial IO I2C Controller #0 /0/100/16 communication Sunrise Point-LP CSME HECI #1 /0/100/1c bridge Intel Corporation /0/100/1c/0displayNVIDIA Corporation /0/100/1c.4bridge Sunrise Point-LP PCI Express Root Port #5 /0/100/1c.6bridge Sunrise Point-LP PCI Express Root Port #7 /0/100/1c.6/0 wlo1networkWireless 8265 / 8275 /0/100/1c.7bridge Sunrise Point-LP PCI Express Root Port #8 /0/100/1c.7/0 genericRTS525A PCI Express Card Reader /0/100/1d bridge Sunrise Point-LP PCI Express Root Port #9 /0/100/1d/0storageToshiba America Info Systems /0/100/1f bridge Intel Corporation /0/100/1f.2memory Memory controller /0/100/1f.3multimedia Intel Corporation /0/100/1f.4busSunrise Point-LP SMBus /1 power KB06079XL $ lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 (rev 07) 00:04.0 Signal processing controller: Intel Corporation Skylake Processor Thermal Subsystem (rev 08) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.6 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #7 (rev f1) 00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 01:00.0 3D controller: NVIDIA Corporation GP108M [GeForce MX150] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0115 (rev 01) $ lsmod | grep multi hid_multitouch 20480 0 hid 118784 4 hid_sensor_hub,i2c_hid,hid_multitouch,intel_ishtp_hid $ modinfo hid_multitouch | grep version srcversion: F120069FA6914E49C917A88 --
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
This bug seems to only affect Xorg. Wayland is not affected (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1725384/comments/18). Since Xorg is not a priority, I suspect this bug is not getting attention. Unfortunately, many of us have to use Xorg (if you have Nvidia hardware, for example). Initially, I thought that perhaps Gnome is generating multiple touch events, causing the apps overview to open, and then close again (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- dock/+bug/1725384/comments/10). However, this could be an issue in Gnome Shell, Gnome Dash, Xorg, specific hardware, or something else entirely. Let's see if we can narrow it down or find some kind of pattern, or clue, to what is going wrong. Doing this may help provide the developers with enough information to spot the cause and fix this bug. It would really useful for all of us to list the hard ware we have... Please share the output of: (1) $ sudo dmidecode | grep -A9 "System Information" (2) $ sudo lshw -short (3) $ lspci (4) Is the multi-touch module loaded (most likely for all of us)... $ lsmod | grep multi (5) Multi-touch module version number... $ modinfo hid_multitouch | grep version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752323] Re: Ubiquity crashes at startup on Kubuntu daily iso - 2018/02/28
Did you `apt update; apt install --reinstall ubiquity` to get the latest version, before launching the installer? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752323 Title: Ubiquity crashes at startup on Kubuntu daily iso - 2018/02/28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1752323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767259] Re: ubuntu 18.04 The 'grub-efi-amd64-signed' package failed to install into / targer.
*** This bug is a duplicate of bug 1767703 *** https://bugs.launchpad.net/bugs/1767703 I also experienced this (Ubuntu 18.04, x64, with EFI enabled on an HP Laptop). During install, I do not have an internet connection enabled. Both checkboxes were disabled: - "Download updates..." - "Install third-party software..." Questions: a) Is the package "grub-efi-amd64-signed" simply not included in the Live CD? [WOULD SOMEONE PLEASE CHECK AND POST THE ANSWER IN THIS BUG REPORT?] If this is the case: Would executing the following in a live session before launching Ubiquity solve the problem?... $ apt install grub-efi-amd64-signed" before launching Ubiquity solve the problem? Should the Live CD come shipped with this package? Should the ubiquity package be updated to include grub-efi-amd64-signed as a "depends" or "recommends"? ...or... b) Does the Ubiquity installer need a newer updated version of this package? [WOULD SOMEONE PLEASE CHECK WHICH VERSION IS INSTALLED AND POST IN THIS BUG REPORT?] If this is the case: Would executing the following in a live session before launching Ubiquity solve the problem?... $ apt update $ apt install grub-efi-amd64-signed" before launching Ubiquity solve the problem? Perhaps Canonical needs to issue a point release Live CD (version 18.04.1?) with an updated version of this package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767259 Title: ubuntu 18.04 The 'grub-efi-amd64-signed' package failed to install into / targer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1767259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778726] Re: 'Details of updates' frame does not expand vertically
Software Updater - How It Should Look ** Attachment added: "Software Updater How It Should Look" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1778726/+attachment/5156786/+files/Software%20Updater%20How%20It%20Should%20Look.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778726 Title: 'Details of updates' frame does not expand vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1778726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778726] [NEW] 'Details of updates' frame does not expand vertically
Public bug reported: SUMMARY There are two expandable sections of the Software Updater window: 1. 'Details of updates' 2. 'Technical description' When the Software Updater window first opens, the 'Details of updates' section is not expand vertically, and an empty 'Technical description' takes 1/2 the vertical space. ISSUE When the Software Updater window first opens, these sections are given the same vertical height, even though 'Technical description' has not been expanded. As a result, 'Details of updates' takes 1/2 the vertical space, and 'Technical description' takes the other 1/2. However nothing is shown in the 'Technical description' section, so Software Updater has a large empty space at the bottom 1/2 of the window. This is especially pronounced if you increase the vertical height of the Software Updater window. See the issue in the attached screenshot 'Software Updater With Bug.png'. STEPS TO RECREATE 1. Open Software Updater when you have updates pending. 2. Notice that the 'Technical description' section is collapsed, so it does not display text. 3. Do _not_ click on the expander triangle next to 'Technical description'. 4. Stretch the Software Updater window vertically using the bottom or top window edge and mouse. 5. Notice that 'Technical description' area takes 1/2 of the vertical window space even though it has not been expanded. **THIS IS THE ISSUE*** 6. Close the Software Updater window. (Do _not_ click Install Now). 7. Open Software Updater (when you have updates pending). 8. Notice that the window 'remembers' its previous size, and is stretched vertically. 9. Notice that 'Technical description' area still takes 1/2 of the vertical window space even though it has not been expanded. **THIS IS THE ISSUE*** 10. Click on the expander triangle next to 'Technical description' 11. A text area appears below 'Technical description'. (It may be blank if you have not selected a package in the 'Details of updates' section, but this is OK). 12. Notice that 'Technical description' area takes 1/2 of the vertical window space, since it has been expanded. This is OK, because there ~is~ a text area to display. 13. Click on the expander triangle next to 'Technical description' again to collapse this section. 14. Notice that 'Technical description' now appears at the _bottom_ of the window. It no longer takes 1/2 the vertical space. The 'Details of updates' frame now uses most of the vertical space, as it should. 15. ***This is how the Software Updater window should look when it first opens in step 2 above.*** HOW IT SHOULD BEHAVE When the Software Updater window first opens: - The 'Technical description' section should be shown near the _bottom_ of the window. - The 'Details of updates' section should be stretched to fill the available vertical space. - The 'Technical description' section should not take 1/2 the vertical space. - The 'Technical description' section should only use 1/2 the vertical space when it is expanded (using the the expander triangle). See the the expected behavior in the attached screenshot 'Software Updater How It Should Look.png'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: update-manager 1:18.04.11 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Aptdaemon: Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jun 26 08:51:21 2018 GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'948' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'586' b'com.ubuntu.update-manager' b'launch-time' b'int64 1530011694' InstallationDate: Installed on 2018-05-09 (48 days ago) InstallationMedia: Ubuntu 18.04.0 2018.05.09 LTS x64 "Custom Bionic Beaver" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Software Updater With Bug" https://bugs.launchpad.net/bugs/1778726/+attachment/5156781/+files/Software%20Updater%20With%20Bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778726 Title: 'Details of updates' frame does not expand vertically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1778726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
I don't use workspaces-to-dock, and I still have the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
I think this bug has been moved to https://gitlab.gnome.org/GNOME/gnome- shell/issues/135 How can we add a remote bug watch for that? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1730211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770299] [NEW] Gjs-WARNING Some code accessed the property 'discreteGpuAvailable'
Public bug reported: I executed gnome-shell --replace from the terminal. After navigating through gnome-shell using my touch screen, I observed the following warnings in the terminal window... (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 9 22:29:33 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-05 (5 days ago) InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: - I executed gnome-shell --restart from the termnal. + I executed gnome-shell --replace from the termnal. - - After navigating through gnome-shell using my touch screen, I observed the following warnings in the terminal window... + After navigating through gnome-shell using my touch screen, I observed + the following warnings in the terminal window... (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed May 9 22:29:33 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-05-05 (5 days ago) InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver" ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - I executed gnome-shell --replace from the termnal. + I executed gnome-shell --replace from the terminal. After navigating through gnome-shell using my touch screen, I observed the following warnings in the terminal window... (gnome-shell:1940): Gjs-WARNING **: 22:17:58.795: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. (gnome-shell:1940): Gjs-WARNING **: 22:17:58.811: Some code accessed the property 'WindowPreviewMenuItem' on the module 'windowPreview'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
If restart gnome-shell using the following in a terminal... gnome-shell --replace ...then the dock behaves normally, launching one instance of an application for each tap I do see some errors after I do this, but they may be unrelated, since it works fine after issuing the above command. (However the error "ubuntu-dock [...] unreachable code after return statement" seems a bit suspicious). $ gnome-shell --replace Gjs-Message: 22:08:47.482: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage" Gjs-Message: 22:08:47.495: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWindowGroup" Gjs-Message: 22:08:47.525: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property "MetaDBusDisplayConfigSkeleton" current session already has an ibus-daemon. Gjs-Message: 22:08:47.759: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActor" GNOME Shell-Message: 22:08:47.804: Telepathy is not available, chat integration will be disabled. Gjs-Message: 22:08:47.998: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1027]: unreachable code after return statement Ubuntu AppIndicators-Message: 22:08:48.361: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.62/org/ayatana/NotificationItem/software_update_available GNOME Shell-Message: 22:08:48.492: Error looking up permission: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for geolocation Gjs-Message: 22:08:57.112: JS WARNING: [resource:///org/gnome/shell/ui/keyboard.js 822]: reference to undefined property "label" (gnome-shell:2512): GLib-GObject-CRITICAL **: 22:09:01.792: g_object_unref: assertion 'G_IS_OBJECT (object)' failed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745888] Re: Two instances of a program launch whenever you touch a favorites icon
Copying the description from duplicate bug #1769540, since there is more information in that description. Also, note that this bug is present in 18.04 (as well as 17.10)... If you touch an icon on the dock using a touch screen, the dock performs duplicate actions for a single touch event. 1. Touching the app-grid icon on the dock with your finger causes the "applications dash" to appear, and quickly disappear, as if you had left-clicked on the app-grid icon *twice* using a mouse button. 2. Touching any favorites icon on the dock with your finger causes the selected application to open *two* instances, as if you had left-clicked on the app-grid icon twice using a mouse button. THIS ONLY AFFECTS UBUNTU-DOCK - This only happens when using the touch screen to interact with the dock. Using a mouse or track-pad works as expected. The top-bar behaves as expected, as well, when using the touch screen. For example, touching the Activities label ovens the "dash overview" as expected; touching the notifications area on the top bar opens the notifications/calendar as expected; touching the indicator icons behave as expected as well. Interacting with open applications using the touch screen also works as expected. Applications respond to touch events as if a single event was generated. UBUNTU DOCK --- Only the ubuntu-dock acts as if it received two (or more) touch events for each single touch action. EXPECTED BEHAVIOR - Ubuntu dock should respond as if it received a single click event, for each single touch event. ADDITIONAL INFORMATION -- If I touch the "Action" item at the top left of the desk-top, the overview appears. THEN, if I touch an icon in the dock, it behaves correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745888 Title: Two instances of a program launch whenever you touch a favorites icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1745888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769540] [NEW] Dock on touch screen does not handle touch events correctly
Public bug reported: If you touch an icon on the dock using a touch screen, the dock performs duplicate actions for a single touch event. 1. Touching the app-grid icon on the dock with your finger causes the "applications dash" to appear, and quickly disappear, as if you had left-clicked on the app-grid icon *twice* using a mouse button. 2. Touching any favorites icon on the dock with your finger causes the selected application to open *two* instances, as if you had left-clicked on the app-grid icon twice using a mouse button. THIS ONLY AFFECTS UBUNTU-DOCK - This only happens when using the touch screen to interact with the dock. Using a mouse or track-pad works as expected. The top-bar behaves as expected, as well, when using the touch screen. For example, touching the Activities label ovens the "dash overview" as expected; touching the notifications area on the top bar opens the notifications/calendar as expected; touching the indicator icons behave as expected as well. Interacting with open applications using the touch screen also works as expected. Applications respond to touch events as if a single event was generated. UBUNTU DOCK --- Only the ubuntu-dock acts as if it received two (or more) touch events for each single touch action. EXPECTED BEHAVIOR - Ubuntu dock should respond as if it received a single click event, for each single touch event. ADDITIONAL INFORMATION -- If I touch the "Action" item at the top left of the desk-top, the overview appears. THEN, if I touch an icon in the dock, it behaves correctly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell-extension-ubuntu-dock 0.9.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 6 20:35:07 2018 InstallationDate: Installed on 2018-05-05 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2018.05.03 LTS "Custom Bionic Beaver" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769540 Title: Dock on touch screen does not handle touch events correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1769540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730211] Re: Unable to type capital letters using onscreen keyboard
This is still an issue on Ubuntu 18.04 using Xorg. Interestingly, capital letters now work on the login GDM screen. But on the desktop, it does't work. Touching the virtual shift key still produces lower case letters. Also, when I select the symbols key to bring up the symbols keyboard layout, not all the keys work. The keys below the top row number of number keys actually produce numbers instead of symbols. Some of the virtual symbols keys do nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730211 Title: Unable to type capital letters using onscreen keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1730211/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Still experiencing this in Bionic 18.04... * Touching the App-Grid icon in the dash-to-dock causes the app icons to appear, and quickly disappear. (It's as if you touched the App-Grid icon twice, very quickly). * Touching a favorites icon in the dash-to-dock causes two instances of the application to open. (It's as if you touched the favorite icon twice, very quickly). $ sudo dmidecode | grep -A9 "System Information" System Information Manufacturer: HP Product Name: HP Spectre x360 Convertible 15-bl1XX Version: Serial Number: 5CD74284QL UUID: 37444335-3234-3438-514C-4C3432344435 Wake-up Type: Power Switch SKU Number: 1VW22AV Family: 103C_5335KV HP Spectre $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic $ uname -a Linux PS006 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ echo $DESKTOP_SESSION gnome-xorg $ gnome-shell --version GNOME Shell 3.28.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
I tried the patch for /usr/lib/ubiquity/ubiquity/misc.py in a virtual machine. Instead of corrupted graphics in the Ubiquity window, I saw a blank white area above the "Copying files..." progress bar. After a few seconds, the Ubiquity slide show appeared as usual, and I did *not* get a crash. I will also try this on actual hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Ubiquity also crashes inside a virtual machine (VirtualBox) running on a non-HiDPI host machine. I have observed corrupted graphics in the "main area" of Ubiquity when this bug occurs. By "main area", I am referring to the rendered rectangular area in Ubiquity below the title bar and above the "Copying files..." progress bar. The corruption looks like jagged diagonal lines or "snow". I have seen this on both actual hardware (HiDPI machine scaled at 200%) and in a virtual machine (non-HiDPI hardware scaled at 100%). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
Here is the backtrace (bt f) with debug symbols. I still have gdb open, if anyone needs me to do anything else? ** Attachment added: "gdb backtrace (bt f) with debug symbols" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5131712/+files/gdb_output_with_debug_symbols.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
*** This bug is a duplicate of bug 1751252 *** https://bugs.launchpad.net/bugs/1751252 @seb128, the three packages libx11-6-dbgsym, libgtk-3-0-dbgsym, libglib2.0-0-dbgsym do not seem to be available in the repositories for bionic. Is there a PPA I need to add, or some other location to get these from? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
Oops, in comment #25, I forgot to attach the installer/debug file. Here it is. ** Attachment added: "installer/debug" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5131119/+files/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
@slashd, I will try again with the command you provided. In the mean time, I was able to use gdb to attach to a running instance of Ubiquity. Here is the backtrace at gdk_x_error. ** Attachment added: "gdb output with backtrace" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5131112/+files/gdb_output_with_backtrace.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
The command gdb file /usr/bin/ubiquity gives the error "not in executable format: File format not recognized" What am I missing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
lspci ** Attachment added: "lspci" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5130958/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
installer/debug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
dmidecode ** Attachment added: "dmidecode" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5130957/+files/dmidecode.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
Contents of installer/version is... ubiquity 18.04.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
syslog after crash ** Attachment added: "syslog after crash" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+attachment/5130956/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
The issue happens using the unmodified official 18.04 live ISO on bare hardware (not virtualzed). I will attach the log files shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] Re: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
I also tried the "Erase and Install" and "Reinstall" options, so this issue happens even when I don't use the "Something else" option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767720] [NEW] Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'
Public bug reported: Ubiquity consistently crashes during install. I use the "Something else" option. It crashes after I've entered the user information and clicked Next. No error message is displayed. If I try to restart Ubiquity, I get a dialog with the message "ubi- partman failed with an exit code 10." If I click the dialog's try again button, I get the same message. My system is broken, and I am only able to install 17.10.1. $ sudo dmidecode | grep -A 9 "System Information" System Information Manufacturer: HP Product Name: HP Spectre x360 Convertible 15-bl1XX Version: Serial Number: 5CD74284QL UUID: 37444335-3234-3438-514C-4C3432344435 Wake-up Type: Power Switch SKU Number: 1VW22AV Family: 103C_5335KV HP Spectre ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 16:13:14 2018 InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/ubuntu-18.04.0-2018.04.28-desktop-amd64.iso noprompt noeject LiveMediaBuild: Ubuntu 18.04.0 2018.04.28 LTS x64 "Custom Bionic Beaver" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767720 Title: Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745888] [NEW] Two instances of a program launch whenever you touch a favorites icon
Public bug reported: Using a touch screen, if you tap on a favorites icon on the ubuntu dock, two (or more) instances of an application launch. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-ubuntu-dock 0.7.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Jan 28 19:47:17 2018 InstallationDate: Installed on 2018-01-28 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2018.01.26 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745888 Title: Two instances of a program launch whenever you touch a favorites icon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1745888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react
My bluetooth mouse is connected now, but I had to follow a special process... WHAT WORKS: I had to turn OFF my wireless, make sure bluetooth was ON, and then connect/pair the mouse. After the bluetooth mouse connected successfully, I was able to turn wi-fi ON again. Now, my mouse automatically connects a few seconds after logging in. It has not disconnected for the brief time I have used it, but I will post back if I notice any new issues. WHAT DOESN'T WORK: * I found that the previous work-around in comment #17 no longer works. * I found that newer kernels did not work either. NOTES ON KERNELS: I tested mainline kernels 4.14.9 thru 4.14.15. All of these newer kernels produce the following error message during installation: "Error! Bad return status for module build on kernel". (Note: this is most likely because I have the Nvidia proprietary drivers version 384.111 installed). However, kernel 4.14.8 installs just fine. But this did not fix the bluetooth problem, until performed the above procedure. OTHER THINGS I TRIED: I did execute "sudo bluetoothctl", and I tried to "trust" and "pair" my mouse from the command line, prior to performing the "wi-fi-off/wi-fi- on" process. However, I do not think "bluetoothctl" helped. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react
I am running artful 17.10.1 with linux-firmware version 1.169.2. I am assuming that version 1.169.2 also has the fix?? In any case, it does not work. Also, the work-around (Comment #17) no longer works for me. $ uname -r 4.13.0-32-generic $ lsb_release --all No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: [Intel 8260/8265] Bluetooth peripherals work for a few seconds, then don't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Note: if you touch "Activities" first, and then touch the Applications Grid Icon, then the dash showing all application icons appears without issue. However, if you have the dock set set to "always show", and you happen to touch the Applications Grid Icon (before tapping the "Activities" label at the top left) then this issue appears. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727318] Re: I can not change Wallpaper after Ubuntu 17.10 Update
I tried to set an svg as my wallpaper by right clicking on it. Then I opened Gnome Control Center. I clicked on Backgrounds in gnome Control center, but Control Center froze. The background id get set after a delay, but I had to kill Control Center. Afterwards, I saw the error in the logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727318 Title: I can not change Wallpaper after Ubuntu 17.10 Update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1727318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737433] [NEW] Ubiquity automatically removes qt5-gtk-platformtheme, but this is needed to integrate KDE apps
Public bug reported: Ubiquity automatically removes qt5-gtk-platformtheme after installing the desktop, but this is needed to make KDE applications look native in Gnome. Ubiquity should not automatically remove this package. This bug affects the Ubuntu 17.10 live iso (ubuntu-17.10-desktop- amd64.iso) and the associated version of Ubiquity. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Dec 10 16:36:41 2017 InstallationDate: Installed on 2017-12-09 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.12.09 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737433 Title: Ubiquity automatically removes qt5-gtk-platformtheme, but this is needed to integrate KDE apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1737433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
** Also affects: gnome-shell via https://bugzilla.gnome.org/show_bug.cgi?id=791427 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731581 Title: Context menus do not appear for Gtk text areas upon right-click To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1731581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
Here is the Bugzilla bug... https://bugzilla.gnome.org/show_bug.cgi?id=791427 ** Bug watch added: GNOME Bug Tracker #791427 https://bugzilla.gnome.org/show_bug.cgi?id=791427 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731581 Title: Context menus do not appear for Gtk text areas upon right-click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
I still see this on shutdown with kernel 4.14. wlo1: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) wlo1: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-22) $ uname -r 4.14.1-041401-generic $ lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 Codename: artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
Patch for /usr/share/grub/default/grub ** Patch added: "Patch for /usr/share/grub/default/grub" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+attachment/5013928/+files/grub.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258597] Re: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported.
This is still present in 17.10. Isn't a permanent fix for this very old bug straightforward?... In the file: /etc/default/grub Comment out or remove: #GRUB_HIDDEN_TIMEOUT=0 #GRUB_HIDDEN_TIMEOUT_QUIET=true Add: GRUB_TIMEOUT_STYLE=hidden Please let me know if I am mistaken about the ease of fixing this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258597 Title: Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT is set is no longer supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1258597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
Same issue as LuisC on 17.10, but using xorg. Also, my keyboard stops working, so I can't press super key. However, the gnome-shell top bar and the Ubuntu Dock still accept inputs. As a result, I am able to launch programs. I can also kill programs by clicking on the window's "X" (close) in Activities (overview) mode, but the window controls (close, minimize, and maximize) do not accept any form of input. Restarting solves the problem. Loging-out and loging back in does not correct the problem. Note that I am able to use the mouse and keyboard on the GDM screen, just like I am able to interact with the topbar and Ubuntu Dock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Here are the results: WORKING: 4.12.0-041200-generic NOT WORKING: 4.13.0-16-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
** Attachment added: "Bluetooth dmesg for Kernel 4.13" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+attachment/5013196/+files/Bluetooth%20with%20kernel%204.13.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
** Attachment added: "Bluetooth dmesg for Kernel 4.12" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+attachment/5013195/+files/Bluetooth%20with%20kernel%204.12.0.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Correction... Kernel 4.12 is working (I had inadvertently selected the wrong kernel on the Grub screen during my last test). $ uname -r 4.12.0-041200-generic I will continue to test 4.12 to see if the Bluetooth mouse unexpectedly disconnects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
So far, not working with 4.14, 4.13, 4.12. With each kernel, I see the messages: Bluetooth: hci0 command 0x0c52 tx timeout Bluetooth: hci0 command 0x0c24 tx timeout I will continue to test older versions and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
After I click on the "Canonical Partners" on the "Other Software" tab, I do ~not~ see an OK button. Also, I am not prompted to enter a password. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
After I click on the "Canonical Partners" on the "Other Software" tab, I do ~not~ see an OK button. Also, I am not prompted to enter a password. ** Attachment added: "No OK button or password dialog after clicking "Canonical Partners" checkbox." https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+attachment/5011992/+files/Screenshot%20from%202017-11-20%2023-39-43.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721315] Re: On-screen keyboard shows up on first touch even when touch does not activate a text-field
*** This bug is a duplicate of bug 1723857 *** https://bugs.launchpad.net/bugs/1723857 Do we know what the desired behavior requirements are? I'm thinking something like... 1. User taps screen 2. Check if event is in an editable text area 3. If yes, display caribou in half* of the screen where tap did ~not~ occur 4. If no, do not display caribou 5. If caribou is not displayed, sliding up from the bottom of the screen should always be available in order to activate the on-screen keyboard. (* Perhaps this could actually be changed to: display caribou in the quadrant of the screen diagonal to where the tap occurred. But you have to take screen size into account, so for smaller screens, the half screen rule above may need to be used). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721315 Title: On-screen keyboard shows up on first touch even when touch does not activate a text-field To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen
Do we know what the desired behavior requirements are? I'm thinking something like... 1. User taps screen 2. Check if event is in an editable text area 3. If yes, display caribou in half* of the screen where tap did ~not~ occur 4. If no, do not display caribou 5. If caribou is not displayed, sliding up from the bottom of the screen should always be available in order to activate the on-screen keyboard. (* Perhaps this could actually be changed to: display caribou in the quadrant of the screen diagonal to where the tap occurred. But you have to take screen size into account, so for smaller screens, the half screen rule above may need to be used). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723857 Title: onscreen keyboard appears whenever i touch touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1723857/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
With 14.14, it only worked for a few seconds and then stopped. $ uname -r 4.14.0-041400-generic Here are some error messages from the logs that may help... hid-generic 0005:03F0:084C.0006: unknown main item tag 0x0 +hid:0005:03F0:084C.0006 bluetoothd Can't get HIDP connection info hid-sensor-hub 001F:8086:22D8.0001: timeout waiting for response from ISHTP device +hid:001F:8086:22D8.0001 bluetoothd Failed to add UUID: Invalid Index (0x11) wpa_supplicant Could not read interface p2p-dev-wlo1 flags: No such device wpa_supplicant dbus: Failed to construct signal Bluetooth: hci0 command 0x0c52 tx timeout ACPI Error: Method parse/execution failed \_SB.WMID.WMAA, AE_AML_BUFFER_LIMIT (20170728/psparse-550) ACPI Error: Field [D128] at bit offset/length 128/1024 exceeds size of target Buffer (160 bits) (20170728/dsopcode-235) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Oops, I meant to write "4.14" (not "14.14") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
If I implement the work-around in comment #17 and use kernel 4.13.12, my bluetooth mouse connects automatically when I reboot. Unfortunately, the work-around seems to still be required for kernel 4.13.12. Let me know if there is anything else I can do to help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Hummm... doesn't look good... Before installing 4.13.12, I reverted the change in comment #17. $ uname -r 4.13.12-041312-generic I see these errors in the logs: bluetoothhd : Failed to add UUID: Not Powered (0x0f) ...and... Bluetooth: hci0 command 0x0c52 tx timeout Also, bluetooth is turned off in the gnome-shell topbar. If I try to open go to Blue Tooth settings from the gnome shell top bar, I get an error that system settings can not be opened; I have an option to Force Quit or Wait. Wait doesn't produce results. $ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: yes Hard blocked: no Going into directly system settings first, and then selecting Bluetooth from the left panel shows that Bluetooth is turned off. If I activate it, nothing shows up in the list of devices. If I navigate away from this in System Settings, and return, again Bluetooth shows as deactivated, but rfkill list does show that it is no longer soft blocked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731724] [NEW] KFileDialog is used for saving files, but the GTK+ dialog should be used
Public bug reported: ISSUE: In KDE applications, such as Kolourpaint, the dialog used to save files is the KFileDialog. EXPECTED BEHAVIOR: The GTK+ dialog should be used for saving files. NOTE: The GTK+ dialog is used to open files and the dialog to save files should also be the GTK+ dialog. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: qt5-gtk-platformtheme 5.9.1+dfsg-10ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 11 22:12:50 2017 InstallationDate: Installed on 2017-11-11 (0 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.10 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qtbase-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731724 Title: KFileDialog is used for saving files, but the GTK+ dialog should be used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1731724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1686802] Re: Locked screen is visible for about a second on resume
Experiencing this on 17.10. It happens on every resume from suspend. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 I am using gnome-session, Xorg, and gdm3. Is this the same as Bug #1416897? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1686802 Title: Locked screen is visible for about a second on resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1686802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen
Experiencing this on 17.10. It happens on every resume from suspend. Distributor ID: Ubuntu Description:Ubuntu 17.10 Release:17.10 I am using gnome-session and Xorg. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1416897 Title: static image of desktop and windows displayed instead of lockscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1416897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731587] Re: Application 'org.gnome.Shell.desktop' killed by signal 11
This is random for me as well, but I have received this error while watching Netflix in Google Chrome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731587 Title: Application 'org.gnome.Shell.desktop' killed by signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1731587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731581] Re: Context menus do not appear for Gtk text areas upon right-click
I just noticed a side-effect which may help in debugging this issue... The mouse cursor does not revert to a pointer after doing a right-click. NORMAL EXPECTED BEHAVIOR (a) Typically, if you are hovering over an editable text area, the mouse pointer is a vertical bar (cursor). when you move outside the text area, such as the window title-bar, the mouse pointer reverts to an arrow. (b) Also, when you right click in a text area, the mouse pointer changes to an arrow, so you can pick something in the pop-up context menu that appears. UNWANTED SIDE-EFFECT BEHAVIOR In this case, right-clicking does not change the cursor to an arrow; it stays as a vertical bar. After this, if you move the pointer outside the text area to the window title bar, the mouse pointer is still a cursor (vertical bar shape). Normal behavior should be as described in (a) above. This also happens for window resize pointers. The mouse pointer stays as a cursor every where in the window after right-clicking in the text area. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731581 Title: Context menus do not appear for Gtk text areas upon right-click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731581] [NEW] Context menus do not appear for Gtk text areas upon right-click
Public bug reported: When right-clicking on Gtk text areas (such as an editable text area or a text entry field), a context menu does not appear. The pop-up context menu typically lists options such as copy, paste, etc. EXAMPLES Examples of applications that are impacted include: 1. Gedit Text Area 2. Nautlus (editable address bar) 3. Google Chrome URL bar 4. GtkHash (text entry fields) Interestingly the text areas of some other applications do show pop-up context menu when right-clicked: 1. Libre Office Writer 2. Web pages in Google Chrome that require text entry (such as this web page) RECREATING ISSUE I do not have a consistent way to recreate this issue (yet). When I first log in, the right-click context menus work fine. After some time of usage, the right-click context menus no longer appear. If I use the computer long enough (over an hour) without rebooting, this issue always appears. This issue seems to only affect widgets that require text entry. However, there is one exception I have noticed: the tabs in Google Chrome stop showing pop-up context menus at the same time as this issues manifests itself for the rest of gnome-shell applications with text areas. OTHER CONTEXT MENUS Context menus for other widgets do appear upon right-click, as expected, and work fine. For example, the context menu for window title bars appear when right-clicking on them. The context menu for folders and files in Nautilus also appear when right-clicking on them. SYSTEM INFORMATION $ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 $ apt-cache policy gnome-shell gnome-shell: Installed: 3.26.1-0ubuntu5 Candidate: 3.26.1-0ubuntu5 Version table: *** 3.26.1-0ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 18:39:00 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['caffe...@patapon.info', 'coverflowalt...@palatis.blogspot.com', 'print...@linux-man.org', 'refresh-w...@kgshank.net', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'cariboubloc...@git.keringar.xyz', 'gpa...@gnome-shell-extensions.gnome.org']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 'gnome-system-monitor.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-11-08 (2 days ago) InstallationMedia: Ubuntu 17.10.0 2017.11.07 amd64 "Custom Artful Aardvark" ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731581 Title: Context menus do not appear for Gtk text areas upon right-click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
It multiple events happen immediately. HOWEVER... I did the same test today, and I get different results... - Sometimes, a single touch on the Dock only does generate a single TouchUpdate event. - Sometimes, a single touch elsewhere on the Screen generates more than one TouchUpdate event. You do have to be very precise with your touch actions to ensure only one TouchUpdate is produced. In general use, multiple TouchUpdate events are generated when you use your finger. I guess this is normal, and the application really just needs to look for a single TouchEnd event. Both the screen and the Dock do generate a single TouchEnd event, and this is probably the important event that applications need to look out for. Nevertheless, in the cases were I was able to cause a single TouchUpdate event on the Dock, I still got the same behavior: - Touching the Applications Grid Button failed to display the applications overview. - I momentarily saw the applications overview expand from the button, and then retract back into the button, as if I had tapped the Applications Grid Button twice, really fast. - Touching an icon on the Dock (favorites) caused two instances of the application to be launched, as if I had tapped the application icon twice, really fast. Does the issue have something to do with the way the Dock handles the TouchEnd events? Caribou (onscreen keyboard) always pops up whenever you touch the screen; could this be influencing the behavior? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730532] Re: Tapping on an icon in the dock launches two instances of the application
*** This bug is a duplicate of bug 1725384 *** https://bugs.launchpad.net/bugs/1725384 Based on information I added to Bug #1725384, this is probably a duplicate, although the symptoms are different. Multiple events are registered for a single tap on the Dock. Touch_Events_For_Dock_2017-11-08-01-PS.txt # (A) TOUCH BEGIN # (B) - TOUCH #1 # (C) - TOUCH #2 # (D) - TOUCH #3 # (E) - TOUCH #4 # (F) - TOUCH #5 # (G) TOUCH END (File is attached to https://bugs.launchpad.net/ubuntu/+source/gnome- shell-extension-ubuntu-dock/+bug/1725384/comments/7) ** This bug has been marked a duplicate of bug 1725384 On touch screens, the apps icon in the dock does not open when touched -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730532 Title: Tapping on an icon in the dock launches two instances of the application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1730532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1730281] Re: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen
*** This bug is a duplicate of bug 1725384 *** https://bugs.launchpad.net/bugs/1725384 ** This bug has been marked a duplicate of bug 1725384 On touch screens, the apps icon in the dock does not open when touched -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1730281 Title: Application icons appear and suddenly disappear when Applications Button is activated via a touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Touch events for the screen, showing 1 event for a single touch, as expected. ** Attachment added: "Touch events for screen" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+attachment/5006288/+files/Touch_Events_For_Screen_2017-11-08-01-PS.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725384] Re: On touch screens, the apps icon in the dock does not open when touched
Using xinput, I captured touch events on the dock's Applications Grid Button. For comparison, I captured touch events on another portion of the screen, away from the dock. The results are very interesting... When I click on the Applications Grid Button on the dock, five (!!) Touch events are registered. These five events are enclosed by only one Touch Begin event and one corresponding Touch End event. However, when I click on another portion of the screen, only one Touch events is registered, enclosed by one Touch Begin event and one corresponding Touch End event. This is how the dock should behave. Please see the attached files. I've inserted comments in the output to make it easy to count the events: Touch_Events_For_Dock_2017-11-08-01-PS.txt # (A) TOUCH BEGIN # (B) - TOUCH #1 # (C) - TOUCH #2 # (D) - TOUCH #3 # (E) - TOUCH #4 # (F) - TOUCH #5 # (G) TOUCH END Touch_Events_For_Screen_2017-11-08-01-PS.txt # (A) TOUCH BEGIN # (B) - TOUCH #1 # (C) TOUCH END Description: Ubuntu 17.10 Release: 17.10 Codename:artful Package: gnome-shell-extension-ubuntu-dock Version: 0.7.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725384 Title: On touch screens, the apps icon in the dock does not open when touched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1725384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
