[Bug 1767586] Re: Boot freezes with Gdm3
If I log out and log in as a different user I get blank screen with mouse cursos visible and movable, but nothing else. If I log in as same user it works or if I boot I can log in with any user. 18.04 normal set up. I did install and purge gnome-session (to test "vanilla gnome"). As a fix I installed lightdm that works fine, but changing to gdm3 will always result into same problem. Sorry, I am not able to give better technical information... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767586 Title: Boot freezes with Gdm3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767586/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
I installed proposed updates. Now it freeze a bit earlier and even more often. Login screen remain visible and no cursor movement while before in looked like progressing with blank screen with cursor movement until final freeze. pe 18. toukok. 2018 klo 19.20 KenWilson (1766...@bugs.launchpad.net) kirjoitti: > Brian, > I attempted to install the proposed package: 3.28.0-0ubuntu1.1 but it > failed. Initially I thought it installed correct but when switching users I > got a notification of a timeout and a package not installed. In the process > of looking at the notification it went away and I don't know how to get it > back. I have included the dpkg log below. I have reverted back to the > standard release and things are working as they were. > > NOTE: the install could be operator error. > > DPKG Log > 2018-05-18 07:53:27 startup archives unpack > 2018-05-18 07:53:38 upgrade gdm3:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:38 status half-configured gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:38 status unpacked gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:38 status half-installed gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:38 status triggers-pending dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:38 status triggers-pending systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:38 status triggers-pending ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:39 status triggers-pending hicolor-icon-theme:all 0.17-2 > 2018-05-18 07:53:40 status triggers-pending man-db:amd64 2.8.3-2 > 2018-05-18 07:53:40 status half-installed gdm3:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:40 status unpacked gdm3:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:41 upgrade libgdm1:amd64 3.28.0-0ubuntu1 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:41 status triggers-pending libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:41 status half-configured libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status unpacked libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:amd64 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:41 status triggers-pending libglib2.0-0:i386 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:41 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status half-installed libgdm1:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:42 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:42 upgrade gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 > 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:42 status half-configured gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1 > 2018-05-18 07:53:42 status half-installed gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1 > 2018-05-18 07:53:43 status half-installed gir1.2-gdm-1.0:amd64 > 3.28.0-0ubuntu1 > 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:43 status unpacked gir1.2-gdm-1.0:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:43 startup packages configure > 2018-05-18 07:53:43 trigproc ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:43 status half-configured ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:44 status installed ureadahead:amd64 0.100.0-20 > 2018-05-18 07:53:44 trigproc libglib2.0-0:amd64 2.56.1-2ubuntu1 > 2018-05-18 07:53:44 status half-configured libglib2.0-0:amd64 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 status installed libglib2.0-0:amd64 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 trigproc libglib2.0-0:i386 2.56.1-2ubuntu1 > 2018-05-18 07:53:46 status half-configured libglib2.0-0:i386 > 2.56.1-2ubuntu1 > 2018-05-18 07:53:47 status installed libglib2.0-0:i386 2.56.1-2ubuntu1 > 2018-05-18 07:53:47 configure libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status unpacked libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status half-configured libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:47 status installed libgdm1:amd64 3.28.0-0ubuntu1.1 > 2018-05-18 07:53:48 trigproc libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 status half-configured libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 status installed libc-bin:amd64 2.27-3ubuntu1 > 2018-05-18 07:53:48 trigproc systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:48 status half-configured systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:51 status installed systemd:amd64 237-3ubuntu10 > 2018-05-18 07:53:51 trigproc man-db:amd64 2.8.3-2 > 2018-05-18 07:53:51 status half-configured man-db:amd64 2.8.3-2 > 2018-05-18 07:53:54 status installed man-db:amd64 2.8.3-2 > 2018-05-18 07:53:54 trigproc dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 status half-configured dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 status installed dbus:amd64 1.12.2-1ubuntu1 > 2018-05-18 07:53:54 trigproc hicolor-icon-theme:all 0.17-2 > 2018-05
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
sorry this is the out come of journalctl /usr/bin/gnome-shell -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 21:03:51 EE huhti 27 22:06:13 ThinkPad-X301 org.gnome.Shell.desktop[762]: glamor: EGL versio huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:16 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:17 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]: Error looking up permission: G huhti 27 22:06:19 ThinkPad-X301 gnome-shell[762]: nma_mobile_providers_database_ huhti 27 22:06:20 ThinkPad-X301 gnome-shell[762]: JS WARNING: [resource:///org/g huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:44 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [resource:///org/ huhti 27 22:06:46 ThinkPad-X301 gnome-shell[1812]: Telepathy is not available, c huhti 27 22:06:49 ThinkPad-X301 gnome-shell[1812]: JS WARNING: [/usr/share/gnome huhti 27 22:06:54 ThinkPad-X301 gnome-shell[1812]: [AppIndicatorSupport-DEBUG] R huhti 27 22:06:56 ThinkPad-X301 gnome-shell[1812]: Object St.BoxLayout (0x561a90 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: == Stack trace fo huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #0 0x73031450 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #1 0x730314b0 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #2 0x73031580 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #3 0x730315f0 huhti 27 22:06:56 ThinkPad-X301 org.gnome.Shell.desktop[1812]: #4 0x561a8f6df7a0 pe 18. toukok. 2018 klo 21.01 Heikki Moisander (moisan...@gmail.com) kirjoitti: > Not sure what came out but this is out come of running journalctl right > after booting after freeze. > I need clear guidance to get something else more relevant. > > Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33 > EE > huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic > (buildd@ > huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: > BOOT_IMAGE=/boot/vmlinuz-4 > huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: > huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel > huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD > huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls > huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations > huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE > huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM > map: > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x0009ec00-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x000dc000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0x0010-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd6a1000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd6a7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd7b7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd80f000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8c7000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d2000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d5000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8d9000-0x000 > huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem > 0xbd8dd000-0x000 > lines 1-23...skipping... > -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 > 20:56:33 EEST. -- > huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic > (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) > #21-Ubunt > huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: > BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic > root=UUID=bf89dfab-58a9-4161-a23c-18da35c20198 ro quie > huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: > huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel > huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD > huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls > huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations > huhti 27 22:06:06 ThinkPad-X301 ker
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Not sure what came out but this is out come of running journalctl right after booting after freeze. I need clear guidance to get something else more relevant. Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33 EE huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic (buildd@ huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4 huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM map: huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0009ec00-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x000dc000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0010-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a1000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd7b7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd80f000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8c7000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d2000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d5000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d9000-0x000 huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8dd000-0x000 lines 1-23...skipping... -- Logs begin at Fri 2018-04-27 22:06:06 EEST, end at Fri 2018-05-18 20:56:33 EEST. -- huhti 27 22:06:06 ThinkPad-X301 kernel: Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubunt huhti 27 22:06:06 ThinkPad-X301 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=bf89dfab-58a9-4161-a23c-18da35c20198 ro quie huhti 27 22:06:06 ThinkPad-X301 kernel: KERNEL supported cpus: huhti 27 22:06:06 ThinkPad-X301 kernel: Intel GenuineIntel huhti 27 22:06:06 ThinkPad-X301 kernel: AMD AuthenticAMD huhti 27 22:06:06 ThinkPad-X301 kernel: Centaur CentaurHauls huhti 27 22:06:06 ThinkPad-X301 kernel: Disabled fast string operations huhti 27 22:06:06 ThinkPad-X301 kernel: x86/fpu: x87 FPU will use FXSAVE huhti 27 22:06:06 ThinkPad-X301 kernel: e820: BIOS-provided physical RAM map: huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x-0x0009ebff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0009ec00-0x0009] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x000dc000-0x000f] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0x0010-0xbd6a0fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a1000-0xbd6a6fff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd6a7000-0xbd7b6fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd7b7000-0xbd80efff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd80f000-0xbd8c6fff] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8c7000-0xbd8d1fff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d2000-0xbd8d4fff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d5000-0xbd8d8fff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8d9000-0xbd8dcfff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8dd000-0xbd8d] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd8e-0xbd906fff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd907000-0xbd907fff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbd908000-0xbdb0efff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdb0f000-0xbdb9efff] ACPI NVS huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdb9f000-0xbdbfefff] ACPI data huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdbff000-0xbdbf] usable huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xbdc0-0xbfff] reserved huhti 27 22:06:06 ThinkPad-X301 kernel: BIOS-e820: [mem 0xe000-0xefff] reserved huhti 27 22:06:
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Really sorry about spamming, but I only now figured out how to get output from relevenant time ( I hope) getUniqueBusNameSync@ /usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:53:49 ThinkPad-X301 gnome-shell[1490]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fre touko 18 20:53:50 ThinkPad-X301 gnome-shell[1490]: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus with touko 18 20:53:53 ThinkPad-X301 gnome-shell[1490]: GNOME Shell started at Fri May 18 2018 20:53:45 GMT+0300 (EEST) touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: Some code accessed the property 'getUniqueBusNameSync' on the module 'util'. That property was defin touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.70/StatusNotifierItem touko 18 20:53:58 Thin getUniqueBusNameSync@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:53:49 ThinkPad-X301 gnome-shell[1490]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.fre touko 18 20:53:50 ThinkPad-X301 gnome-shell[1490]: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus with touko 18 20:53:53 ThinkPad-X301 gnome-shell[1490]: GNOME Shell started at Fri May 18 2018 20:53:45 GMT+0300 (EEST) touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: Some code accessed the property 'getUniqueBusNameSync' on the module 'util'. That property was defin touko 18 20:53:55 ThinkPad-X301 gnome-shell[1490]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.70/StatusNotifierItem touko 18 20:53:58 ThinkPad-X301 gnome-shell[1490]: Some code accessed the property 'refreshPropertyOnProxy' on the module 'util'. That property was def touko 18 20:54:08 ThinkPad-X301 gnome-shell[1490]: JS WARNING: [resource:///org/gnome/shell/ui/endSessionDialog.js 763]: reference to undefined propert touko 18 20:54:11 ThinkPad-X301 gnome-shell[1490]: gnome-shell: Fatal IO error 0 (Onnistui) on X server :0. -- Reboot -- touko 18 20:55:42 ThinkPad-X301 org.gnome.Shell.desktop[934]: glamor: EGL version 1.4 (DRI2): touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage" touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWind touko 18 20:55:44 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined property touko 18 20:55:45 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyActo touko 18 20:55:46 ThinkPad-X301 gnome-shell[934]: Unable to connect to ibus: Yhdistäminen ei onnistunut: Yhteys torjuttu touko 18 20:55:47 ThinkPad-X301 gnome-shell[934]: Error looking up permission: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.free touko 18 20:55:47 ThinkPad-X301 gnome-shell[934]: JS WARNING: [resource:///org/gnome/shell/ui/windowManager.js 1468]: reference to undefined property " touko 18 20:55:49 ThinkPad-X301 gnome-shell[934]: nma_mobile_providers_database_lookup_cdma_sid: assertion 'sid > 0' failed touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/main.js 340]: reference to undefined property "MetaStage touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/layout.js 220]: reference to undefined property "MetaWin touko 18 20:56:05 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/osdMonitorLabeler.js 59]: reference to undefined propert touko 18 20:56:06 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [resource:///org/gnome/shell/ui/slider.js 38]: reference to undefined property "CallyAct touko 18 20:56:07 ThinkPad-X301 gnome-shell[1545]: Telepathy is not available, chat integration will be disabled. touko 18 20:56:09 ThinkPad-X301 gnome-shell[1545]: JS WARNING: [/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js 1027]: unreachable touko 18 20:56:11 ThinkPad-X301 gnome-shell[1545]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get owner getUniqueBusNameSync@ /usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:58:20 traverseBusNames/<@/usr/share/gnome-shell/extensions/ ubuntu-appindicat...@ubuntu.com/util.js:82:34 touko 18 20:56:12 ThinkPad-X301 gnome-shell
[Bug 1772268] [NEW] User change login freeze
Public bug reported: While trying to change to another user account without boot display manager freeze. ctr-alt-F2 return back to previous user. While trying to log in to another user account after log out from another result to same immediate freeze. ctr-alt-del boots and after this login works. I am using ubuntu 18.04 fresh install with final release. I have checked yes to the the bionic-proposed as similar kind of bug was reported to have a fix available. gdm3: Asennettu: 3.28.0-0ubuntu1.1 Ehdokas: 3.28.0-0ubuntu1.1 Versiotaulukko: *** 3.28.0-0ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 Uname: Linux 4.15.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Sun May 20 17:55:27 2018 InstallationDate: Installed on 2018-04-27 (22 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [deleted] ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772268 Title: User change login freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772268] Re: User change login freeze
I did run "ubuntu-bug /var/crash/_usr_lib_gnome-session_gnome-session-check-accelerated.120.crash" Looked like it was sent. This bug shows up differently copared to 1766137. This time login will not progress to blank screen and probability is 100% now as bug 1766137 showed up to me only maybe 50-70% of the time. I don't know what is the definition of being the same bug. Looks like different and there was fix for 1766137 so I guess this is different? ma 21. toukok. 2018 klo 5.35 Daniel van Vugt (daniel.van.v...@canonical.com) kirjoitti: > Also, does the bug look like bug 1766137 ? > > ** Changed in: gdm3 (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1772268 > > Title: > User change login freeze > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > While trying to change to another user account without boot display > manager freeze. ctr-alt-F2 return back to previous user. While trying > to log in to another user account after log out from another result to > same immediate freeze. ctr-alt-del boots and after this login works. > > I am using ubuntu 18.04 fresh install with final release. I have > checked yes to the the bionic-proposed as similar kind of bug was > reported to have a fix available. > > gdm3: > Asennettu: 3.28.0-0ubuntu1.1 > Ehdokas: 3.28.0-0ubuntu1.1 > Versiotaulukko: >*** 3.28.0-0ubuntu1.1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main > amd64 Packages > 100 /var/lib/dpkg/status >3.28.0-0ubuntu1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 > Packages > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gdm3 3.28.0-0ubuntu1.1 > ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 > Uname: Linux 4.15.0-21-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > Date: Sun May 20 17:55:27 2018 > InstallationDate: Installed on 2018-04-27 (22 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >LANG=fi_FI.UTF-8 >SHELL=/bin/bash > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > modified.conffile..etc.gdm3.custom.conf: [deleted] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772268/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772268 Title: User change login freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1772268] Re: User change login freeze
2018-05-18 17:05 2018-05-18 14:05 UTC Crash gnome-session-bin link: https://errors.ubuntu.com/oops/d6ec2448-5aa9-11e8-8106-fa163ef911dc ma 21. toukok. 2018 klo 10.11 Daniel van Vugt (daniel.van.v...@canonical.com) kirjoitti: > Bug 1766137 is not fixed in 18.04 yet. Only in 18.10. So it may still be > related. But let's not assume it's the same bug yet... > > Please have a look at this link to review crash reports send by your > system: > https://errors.ubuntu.com/user/ID > where ID is the contents of /var/lib/whoopsie/whoopsie-id > And tell us the links of recent reports you find there. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1772268 > > Title: > User change login freeze > > Status in gdm3 package in Ubuntu: > Incomplete > > Bug description: > While trying to change to another user account without boot display > manager freeze. ctr-alt-F2 return back to previous user. While trying > to log in to another user account after log out from another result to > same immediate freeze. ctr-alt-del boots and after this login works. > > I am using ubuntu 18.04 fresh install with final release. I have > checked yes to the the bionic-proposed as similar kind of bug was > reported to have a fix available. > > gdm3: > Asennettu: 3.28.0-0ubuntu1.1 > Ehdokas: 3.28.0-0ubuntu1.1 > Versiotaulukko: >*** 3.28.0-0ubuntu1.1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main > amd64 Packages > 100 /var/lib/dpkg/status >3.28.0-0ubuntu1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 > Packages > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gdm3 3.28.0-0ubuntu1.1 > ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17 > Uname: Linux 4.15.0-21-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > Date: Sun May 20 17:55:27 2018 > InstallationDate: Installed on 2018-04-27 (22 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >LANG=fi_FI.UTF-8 >SHELL=/bin/bash > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > modified.conffile..etc.gdm3.custom.conf: [deleted] > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772268/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772268 Title: User change login freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1772268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768619] [NEW] gdm3 crashes on login
Public bug reported: Login works on start up, but when logged out and login in with another user end up blank screen with only moving cursor. Will not make any difference using xorg or wayland. It is failing some 15 times out of 20 tryout. Sometimes it boots by itself sometime ctrl+alt+del seem to result into boot and sometimes only cutting out power will enable boot. So gdm3 is useless to our purpose as we share always on pc's within our team. I am pretty sure it is a bug. There would not be option to log out, if only restart makes it possible to logout and login with different user, though fix could be removing that possibility. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed May 2 20:23:31 2018 InstallationDate: Installed on 2018-04-27 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [deleted] ** Affects: gdm3 (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/1768619 Title: gdm3 crashes on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Work around does not work for. It is not about nvidia driver. Lets face it, it is a showstopper for ubuntu 18.04 until bug is fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873686] [NEW] cut action fails to save content to clipboard or fails to use in in paste
Public bug reported: I tried to report the bug as Libreoffice bug, but they seem to ignore it as of problem in ubuntu. I was advised to report this for ubuntu beta 20.04. Bugzilla Bug 132213 shows what I was able to describe at the time. I dis some 50 cut and paste actions while working with LibreOffice calc document. 3 times cut operation succeeded but paste result was what was cut and already pasted during previous cut and paste sequence. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873686 Title: cut action fails to save content to clipboard or fails to use in in paste To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
I updated proposed mutter 3.36.2 and tried Libreoffice Calc sheet copy - paste, cut - paste in pretty much same way with the same pc I did at the time I reported the bug - only few times more. I did not run into error. I don't have any need for extensive copy - paste activity any time soon, so will not get any additional testing done. On Fri, 15 May 2020 at 16:25, Guillem Solivellas <1852...@bugs.launchpad.net> wrote: > I can tell you it's not. When using the cut-and-paste feature from > LibreOffice 8not first time..., the second and next...) you need to do the > copy action twice to get your string stored. > > > garrig...@gmail.com > > > Missatge de Adam Dingle del dia dv., 15 de maig 2020 a > les 6:26: > > > Hi Daniel - I'm the one who first reported this Launchpad bug back in > > November. :) I'm very happy to see that there is a proposed fix, since > > I (like many others) have continued to experience this bug on a daily > > basis for many months now. I appreciate your asking my opinion, though > > it certainly should not be the only one that counts here. > > > > I am running Focal (20.04) and I just installed the proposed > > 3.36.2-1ubuntu1~20.04.1 package. I'll need to run with it for a day or > > two before I'll have an opinion about whether the fix is adequate. Keep > > fingers crossed. :) > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1876445). > > https://bugs.launchpad.net/bugs/1852183 > > > > Title: > > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > > comment 93) > > > > Status in LibreOffice: > > Won't Fix > > Status in Mutter: > > Unknown > > Status in mutter package in Ubuntu: > > Fix Released > > Status in mutter source package in Eoan: > > Triaged > > Status in mutter source package in Focal: > > Fix Committed > > Status in mutter source package in Groovy: > > Fix Released > > > > Bug description: > > [ Impact ] > > > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > > > In this environment, copy/cut/paste often fails. Specifically, the > > paste command sometimes does not paste the text that was cut/copied > > most recently. Instead, it pastes text that was cut/copied at some > > prior time. > > > > [ Test case ] > > > > 1. Use use libreoffice writer/calc > > 2. Copy text around > > 3. Paste it and ensure it always work > > > > [ Regression potential ] > > > > Copy/paste won't work as expected, for non-text types > > > > - > > > > > > I use LibreOffice Writer a lot, and I now see this problem very often, > > i.e. many times every day. > > > > There is some discussion of the problem here: > > > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > > libreoffice-calc/ > > > > Several posters there say that they are also using Ubuntu 19.10. > > > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > > > https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 > > -Clipboard-Manager > > > > It seems like that could be related. > > > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873686). > https://bugs.launchpad.net/bugs/1852183 > > Title: > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > comment 93) > > Status in LibreOffice: > Won't Fix > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Eoan: > Triaged > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > [ Impact ] > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > In this environment, copy/cut/paste often fails. Specifically, the > paste command sometimes does not paste the text that was cut/copied > most recently. Instead, it pastes text that was cut/copied at some > prior time. > > [ Test case ] > > 1. Use use libreoffice writer/calc > 2. Copy text around > 3. Paste it and ensure it always work > > [ Regression potential ] > > Copy/paste won't work as expected, for non-text types > > - > > > I use LibreOffice Writer a lot, and I now see this problem very often, > i.e. many times every day. > > There is some discussion of the problem here: > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > libreoffice-calc/ > > Several posters there say that they are also using Ubuntu 19.10. > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 > -Clipboard-Manager > > It seems like that could be related. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/df-libreoffice/+bug/185218
Re: [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
If there is a possibility that copy-paste will result to an error, whole distro is useless for serious production use. It is really sad, testing this kind of bug is so uncertain and difficult. In my opinion programmer should be able to guarantee that such error can not take place. Otherwise there are something fundamentally wrong in design. Sorry, I am a big fan of Ubuntu and would like to see open source success in office environment, but this bug seems a show stopper for me if community is incapable of fixing it 100%. On Mon, 18 May 2020 at 07:05, Adam Dingle wrote: > Once again I am the original reporter - Daniel recently asked for my > opinion about whether this bug has been fixed. > > I have now been running with the proposed 3.36.2-1ubuntu1~20.04.1 > package for three days, during which I have done a fair amount of > editing with copying and pasting. During that time I saw this > copy/paste bug occur twice: once on 5/16 when I couldn't copy and paste > from Epiphany (a web browser) to gedit, and once on 5/17 when I couldn't > copy and paste from a LibreOffice Writer window into another LibreOffice > Writer window. > > My opinion is that the proposed fix is a definite improvement, because I > am sure that without it I would have seen more copy/paste failures these > last few days. However I believe that the bug is still not completely > fixed. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873686). > https://bugs.launchpad.net/bugs/1852183 > > Title: > [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > comment 93) > > Status in LibreOffice: > Won't Fix > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Eoan: > Triaged > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > [ Impact ] > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > In this environment, copy/cut/paste often fails. Specifically, the > paste command sometimes does not paste the text that was cut/copied > most recently. Instead, it pastes text that was cut/copied at some > prior time. > > [ Test case ] > > 1. Use use libreoffice writer/calc > 2. Copy text around > 3. Paste it and ensure it always work > > [ Regression potential ] > > Copy/paste won't work as expected, for non-text types > > - > > > I use LibreOffice Writer a lot, and I now see this problem very often, > i.e. many times every day. > > There is some discussion of the problem here: > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > libreoffice-calc/ > > Several posters there say that they are also using Ubuntu 19.10. > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 > -Clipboard-Manager > > It seems like that could be related. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see comment 93)
It was really meant to be helpful. You should understand this kind of bug is truly critical. I believe this has not been the case. I am sorry, I am not able to help in any other way for now and will not participate in any further discussions or bug reporting. I wish you all the best. On Mon, 18 May 2020 at 07:50, Daniel van Vugt wrote: > That's not a helpful comment. > > Many of us actually have never encountered this bug so to say "whole > distro is useless for serious production use" is grossly inaccurate. And > even those who do encounter this bug would not say it makes Ubuntu > "useless". > > Please only comment if you have productive, useful, information to add. > And if you continue to experience any problems please report them by > opening a new bug with the command: > > ubuntu-bug mutter > > and/or reporting them to the developers at: > > https://gitlab.gnome.org/GNOME/mutter/-/issues > > > ** Summary changed: > > - [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 (see > comment 93) > + [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 > & 20.04 (see comment 93) > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1873686). > https://bugs.launchpad.net/bugs/1852183 > > Title: > [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu > 19.10 & 20.04 (see comment 93) > > Status in LibreOffice: > Won't Fix > Status in Mutter: > Unknown > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Eoan: > Triaged > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > [ Impact ] > > I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. > > In this environment, copy/cut/paste often fails. Specifically, the > paste command sometimes does not paste the text that was cut/copied > most recently. Instead, it pastes text that was cut/copied at some > prior time. > > [ Test case ] > > 1. Use use libreoffice writer/calc > 2. Copy text around > 3. Paste it and ensure it always work > > [ Regression potential ] > > Copy/paste won't work as expected, for non-text types > > - > > > I use LibreOffice Writer a lot, and I now see this problem very often, > i.e. many times every day. > > There is some discussion of the problem here: > > https://ask.libreoffice.org/en/question/213510/copypaste-issues- > libreoffice-calc/ > > Several posters there say that they are also using Ubuntu 19.10. > > Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: > > https://www.phoronix.com/scan.php?page=news_item&px=GNOME-3.34 > -Clipboard-Manager > > It seems like that could be related. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1715365] Re: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()
I partly agree. Users don't bother to report the bugs as it is difficult and as this is free software and complaining feels unjustified. However I am simply not able to put enough effort to prove my point (will be too busy for that now). It is incredible that basic functionality is at such a poor level. Bug appears to an ordinary user so vaguely that bug reporting fails to show the cause of the problem. The most serious problems have been somehow fixed, but it is still a shameful quality (standard ubuntu 18.04 clean install few months ago). Often we need to boot to be able to change the user (sorry if you feel this is spam ... this message was inspired by one such occasion again). ke 23. tammik. 2019 klo 21.00 Johanna Müller (1715...@bugs.launchpad.net) kirjoitti: > Such a basic funcionality as switching users is not working since 1.5 > years and there is still nobody assigned to that critical issue? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1772268). > https://bugs.launchpad.net/bugs/1715365 > > Title: > gnome-session-check-accelerated crashed with SIGSEGV in > g_hash_table_lookup_node() from g_hash_table_lookup() from > lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display() > > Status in gnome-session package in Ubuntu: > Confirmed > > Bug description: > Possibly: > > https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f > > https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a > > --- > > bug at login > > ProblemType: Crash > DistroRelease: Ubuntu 17.10 > Package: gnome-session-bin 3.25.90-0ubuntu2 > Uname: Linux 4.12.0-041200-generic x86_64 > ApportVersion: 2.20.7-0ubuntu1 > Architecture: amd64 > CurrentDesktop: GNOME-Greeter:GNOME > Date: Sun Sep 3 09:34:09 2017 > Disassembly: => 0x0: Cannot access memory at address 0x0 > ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated > InstallationDate: Installed on 2015-04-16 (874 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 > (20141022.1) > ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated > SegvAnalysis: >Segfault happened at: 0x0: Cannot access memory at address 0x0 >PC (0x) not located in a known VMA region (needed executable > region)! > SegvReason: executing NULL VMA > Signal: 11 > SourcePackage: gnome-session > StacktraceTop: >() >g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 >gdk_x11_atom_to_xatom_for_display () at > /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 >() >__libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8, > init=, fini=, rtld_fini=, > stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291 > Title: gnome-session-check-accelerated crashed with SIGSEGV > UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago) > UserGroups: > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1715365/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715365 Title: gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1715365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Mostly I don't understand this discussion and probably I should not take part in it. There has been no progress visible to me. The bug I reported was assigned as duplicate to this, so if this is now fixed, should I report the bug again? Anyhow it appears to me, that to ordinary users sharing the PC, 18.04 is useless without changing back to lightdm (I hope that still works after latest development.) In practice that is not an option to most basic users, so going back to 16.04 or another distro is likely the choice. I am confused after reading all this development discussion. I would assume this is being fixed, but getting worried. ti 29. toukok. 2018 klo 5.05 Daniel van Vugt (daniel.van.v...@canonical.com) kirjoitti: > Marco, > > It sounds like you're talking about the secondary bug. So let's reopen > the cosmic task, awaiting that second fix. Cosmic presently has gdm3 > 3.28.0-0ubuntu2. > > ** Changed in: gdm3 (Ubuntu) >Status: Fix Released => In Progress > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > In Progress > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > In Progress > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a fresh install, and didn't occur when I was using a previous > install of 18.04 (until Friday). > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gdm3 3.28.0-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 > Uname: Linux 4.15.0-15-generic x86_64 > ApportVersion: 2.20.9-0ubuntu6 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 22 20:31:13 2018 > InstallationDate: Installed on 2018-04-22 (0 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180421.1) > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blan
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
heikki@ThinkPad-X301:~$ apt-cache policy gdm3 gdm3: Asennettu: 3.28.2-0ubuntu1.1 Ehdokas: 3.28.2-0ubuntu1.1 Versiotaulukko: *** 3.28.2-0ubuntu1.1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.28.0-0ubuntu1 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I seem to have fixed version now. It does not work for me any different from the previous version. Nothing happens while trying to change user or log in with different user account. After trying I can get back to login screen but then only way to login is boot. ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (1766...@bugs.launchpad.net) kirjoitti: > Hello Chris, or anyone else affected, > > Accepted gdm3 into bionic-proposed. The package will build now and be > available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 > in a few hours, and then in the -proposed repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed.Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested and change the tag from > verification-needed-bionic to verification-done-bionic. If it does not > fix the bug for you, please add a comment stating that, and change the > tag to verification-failed-bionic. In either case, without details of > your testing we will not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance! > > ** Changed in: gdm3 (Ubuntu Bionic) >Status: In Progress => Fix Committed > > ** Tags removed: verification-failed-bionic > ** Tags added: verification-needed-bionic > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > In Progress > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Sorry I commented too quickly below after first tryout. After couple of boots and tryouts it did finally succeed after longer wait time and now after testing some 5 times I have managed to log with different user after loging out. it is slow, but it will get there. So certainly I see good progress, looks better now. ti 29. toukok. 2018 klo 22.47 Heikki Moisander (moisan...@gmail.com) kirjoitti: > heikki@ThinkPad-X301:~$ apt-cache policy gdm3 > gdm3: > Asennettu: 3.28.2-0ubuntu1.1 > Ehdokas: 3.28.2-0ubuntu1.1 > Versiotaulukko: > *** 3.28.2-0ubuntu1.1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic-proposed/main > amd64 Packages > 100 /var/lib/dpkg/status > 3.28.0-0ubuntu1 500 > 500 http://fi.archive.ubuntu.com/ubuntu bionic/main amd64 Packages > > I seem to have fixed version now. It does not work for me any different > from the previous version. Nothing happens while trying to change user or > log in with different user account. After trying I can get back to login > screen but then only way to login is boot. > > ti 29. toukok. 2018 klo 17.31 Łukasz Zemczak (1766...@bugs.launchpad.net) > kirjoitti: > >> Hello Chris, or anyone else affected, >> >> Accepted gdm3 into bionic-proposed. The package will build now and be >> available at https://launchpad.net/ubuntu/+source/gdm3/3.28.2-0ubuntu1.1 >> in a few hours, and then in the -proposed repository. >> >> Please help us by testing this new package. See >> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how >> to enable and use -proposed.Your feedback will aid us getting this >> update out to other Ubuntu users. >> >> If this package fixes the bug for you, please add a comment to this bug, >> mentioning the version of the package you tested and change the tag from >> verification-needed-bionic to verification-done-bionic. If it does not >> fix the bug for you, please add a comment stating that, and change the >> tag to verification-failed-bionic. In either case, without details of >> your testing we will not be able to proceed. >> >> Further information regarding the verification process can be found at >> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in >> advance! >> >> ** Changed in: gdm3 (Ubuntu Bionic) >>Status: In Progress => Fix Committed >> >> ** Tags removed: verification-failed-bionic >> ** Tags added: verification-needed-bionic >> >> -- >> You received this bug notification because you are subscribed to a >> duplicate bug report (1768619). >> https://bugs.launchpad.net/bugs/1766137 >> >> Title: >> [regression] Password accepted but login fails (blank purple screen >> and mouse pointer only) >> >> Status in gdm: >> Fix Released >> Status in Release Notes for Ubuntu: >> Fix Released >> Status in gdm3 package in Ubuntu: >> In Progress >> Status in gnome-shell package in Ubuntu: >> Invalid >> Status in gdm3 source package in Bionic: >> Fix Committed >> Status in gnome-shell source package in Bionic: >> Invalid >> >> Bug description: >> [ Description ] >> >> Due to a refcounting bug, a GDBusConnection was getting disposed when >> it was still required. The symptom of this was that you couldn't log >> in on the second attempt if you'd got your password wrong on the first >> attempt. All you'd see is a blank purple screen and mouse pointer >> only. >> >> [ Test case ] >> >> 1. Boot to GDM >> 2. Click your username >> 3. Type the wrong password a couple of times, pressing enter after each >> time >> 4. Type the right password >> >> If the bug is happening, after 4. the system hangs at a blank screen >> with the mouse cursor. If you then switch to a VT or otherwise connect >> to the machine, you can examine the journal and you'll see a >> G_IS_DBUS_CONNECTION failure. >> >> [ Fix ] >> >> Marco and I worked upstream on this fix. We found out that there was a >> problem like this- >> >> The GdmClient has a shared GDBusConnection for its operations. The >> first time someone calls for it, it is created and stored in the >> object's private structure. Subsequent calls return *a new reference* >> to this same object. It turned out that the asynchronous method to get >> the connection was accidentally unreferencing its object before giving >> it to the caller if it was returning an already-existing connection. >> >>
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Did you test : 3.28.2-0ubuntu1.1 ? I thought that is The version having The fix ke 30. toukokuuta 2018 klo 18.51 KenWilson <1766...@bugs.launchpad.net> kirjoitti: > All, > My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect password > issue; however, it creates a new issue. As such I don’t think this update > should be released. > > I installed gdm3 3.28.0-0ubuntu1.1 and rebooted my system (Ubuntu 18.04 > LTS). Making sure I typed the password correct I was able to login to > each account on the system. I then logged out and performed the > following steps to ensure the password issue was resolved. > > For two accounts I performed the following steps three times for each. > Each time succeeded. > > 1. I typed a bad password and pressed enter. I did this two times. > Each time I was returned to the login screen and received a message the > login didn’t work. > 2. I then typed a correct password and successfully logged in. > 3. I then locked the screen and performed steps one and two and each > time it worked as it should. > 4. I then logged out of the account and performed steps one and two > and each time it worked as it should. > Based on this testing I would say recovering from a bad password is fixed. > > The next test I performed was to login into one account and then switch > to the other account. I was able to successfully switch to the other > account. I then tried to switch back to the first account but I was > never able to successfully switch back. I tried it at least six times > and in no case did it work. It did not matter which account I logged > into first I was never able to switch to the other then switch back. In > each case when I switched the second time the system hung and I could > not find a way to recover. I tried CTRL+ALT+F2, CTRL+ALT+F1, CTRL+ALT+F2 > but there was still unable to login. I was not able to login to any > account even when being extremely careful the password was correct. > > I then reinstalled gdm3 3.28.0-0ubuntu1 and tried switching between > accounts. As long as I ensure I type the password correct I can switch > between accounts multiple times without issue. If I type an incorrect > password I can do CTR+ALT+F2, CTRL+ALT+F1, CTRL+ALT+F2 to recover. > > With package gdm3 3.28.0-0ubuntu1.1 the only way I was able to regain > control (after trying to switch accounts a second time) was with a > system reboot. To me, having to reboot is a catastrophic failure and > therefor this package should not be released. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > Fix Released > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
I had similar experience yesterday after installing 3.28.2 and I reported that it does not work. But after couple of boots I have been testing every now and then maybe some 15 times and every time it has logged in - very slowly but success anyway. To me that is quite clear that any kind of success is better that need to boot every time. It is not about speed, but we can not accept the situation user get frozen screen every time login in after someone else. So if anything better is not available please take this into production. ke 30. toukokuuta 2018 klo 20.11 KenWilson <1766...@bugs.launchpad.net> kirjoitti: > I installed package 3.28.2-0ubuntu1.1 and performed the testing again. I > restricted testing to only switching between accounts. Same result, it > did not work. > > Listing... Done > gdm3/bionic-proposed,now 3.28.2-0ubuntu1.1 amd64 [installed] > gdm3/bionic 3.28.0-0ubuntu1 amd64 > > After installation I rebooted my system. I successfully logged into > “account A”. I successfully switched to “account B”. I then tried to > switch back to “account A” but was not successful. I am stuck at the > login screen. I cannot login to either “account A” or “account B”. I had > to reboot to gain control of my system. > > Ken > > > On 05/30/2018 09:06 AM, Iain Lane wrote: > > On Wed, May 30, 2018 at 03:45:17PM -, KenWilson wrote: > >> All, > >> My testing indicates gdm3 3.28.0-0ubuntu1.1 fixes the incorrect > >> password issue; however, it creates a new issue. As such I don’t think > >> this update should be released. > > That verison is superseded by 3.28.2-0ubuntu1.1. Please try this one. > > > > -- > *Ken Wilson* > lake > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > Fix Released > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a fresh install, and didn't occur when I was using a previous > install of 18.04 (until Friday). > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gdm3 3.28.0-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 > Uname: Linux 4.15.0-15-generic x86_64 > ApportVersion
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Fresh install 18.04 gdm3 did succeed occasionally, but mostly froze completely so that power button was only way out. There was a fix that was available in proposed repository (or something) that made things a bit different. Failure became a rule, but it was possible to get back with ctrl+alt+F1/F2 (randomly pressing both) Now this latest version is the first one that seems to work everytime. My personal wish would be that please stop complicating the thing and put it in production. to 31. toukok. 2018 klo 6.55 Jehandan Jeyaseelan (1766...@bugs.launchpad.net) kirjoitti: > Hi, > > In addition to my post #96 above, I downgraded gdm3 back to the release > version - 3.28.0-0ubuntu1 and am able to confirm that switching users > works perfectly between two users for me. > > Therefore sounds like the fix for gdm3 - 3.28.2-0ubuntu1.1 - has > introduced further issues. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > Fix Released > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a fresh install, and didn't occur when I was using a previous > install of 18.04 (until Friday). > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gdm3 3.28.0-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 > Uname: Linux 4.15.0-15-generic x86_64 > ApportVersion: 2.20.9-0ubuntu6 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sun Apr 22 20:31:13 2018 > InstallationDate: Installed on 2018-04-22 (0 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20180421.1) > SourcePackage: gdm3 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.la
[Bug 1784476] [NEW] Trusted and paired blueltooth keyboard available only after login
Public bug reported: Logitec K800 and logitec M535 worked perfectly with Ubuntu 16.04. I can pair the keybord alone and everything works, but mouse M535 can not be paird at all with default bluetooth settings so that it would work after boot. However using blueman M535 can be successfully paired, but then keyboard k800 will not be visible at login time. It will eventually work after login in. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Jul 30 22:38:23 2018 InstallationDate: Installed on 2018-07-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: System manufacturer System Product Name PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=cb36aad0-035d-44fa-a0ab-74aa16b0ca3c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M LE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd01/18/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:02:72:37:65:6E ACL MTU: 1022:8 SCO MTU: 121:3 UP RUNNING PSCAN ISCAN RX bytes:36235 acl:1906 sco:0 events:349 errors:0 TX bytes:7333 acl:125 sco:0 commands:106 errors:0 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (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/1784476 Title: Trusted and paired blueltooth keyboard available only after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1784476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
3.28.2-0ubuntu1.1 did work fine for login logout to another user (critical in our environment). It has been few days since it was supposed to be coming and I figured that it is safe now to start installing 18.04, but fresh install 18.04 and I am still getting 3.28.0-Oubuntu1 - will not work. su 10. kesäk. 2018 klo 17.25 OliFre (1766...@bugs.launchpad.net) kirjoitti: > @Ads2 Thanks for the link. Sadly, gdm3 is neither in the > autopkgtest-list, nor update-excuses, nor update-list, so it seems > things are stuck at an earlier stage and the documentation does not > clarify where to find out at which point help could be needed. > > My intention was not to spam this report, but to find out where things are > stuck (it's not obvious) and how to give support. > It's also not about my personal (im)patience, but we have >200 desktops > and >2000 Ubuntu containers and have had to stop the migration after the > first 10 desktops due to this bug (and three(!) other ones which all have > been known *before* release and should either have been release blockers or > been mentioned as "Known Issues" with the new LTS to prevent people from > hopping onto the new supposedly-stable). For the other critical issues, QA > apparently was even worse, since Debian and in one case also RHEL have > already released fixes months or even a year ago, and there has been no > reaction on Launchpad whatsoever yet. Since we are also still affected by > critical bugs in 16.04 which have been open since 16.04's release and could > only be solved by PPA (broken OpenAFS), this makes me wonder whether Ubuntu > still is a valid choice for institutional use, but this discussion > certainly goes off topic here. > > Just let us know if there is something people could help with (testing > etc.). As it stands, the status is completely unclear apart from the > statement _to be patient_ - without indicating what the actual point is > where things are stuck. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1768619). > https://bugs.launchpad.net/bugs/1766137 > > Title: > [regression] Password accepted but login fails (blank purple screen > and mouse pointer only) > > Status in gdm: > Fix Released > Status in Release Notes for Ubuntu: > Fix Released > Status in gdm3 package in Ubuntu: > Fix Released > Status in gnome-shell package in Ubuntu: > Invalid > Status in gdm3 source package in Bionic: > Fix Committed > Status in gnome-shell source package in Bionic: > Invalid > > Bug description: > [ Description ] > > Due to a refcounting bug, a GDBusConnection was getting disposed when > it was still required. The symptom of this was that you couldn't log > in on the second attempt if you'd got your password wrong on the first > attempt. All you'd see is a blank purple screen and mouse pointer > only. > > [ Test case ] > > 1. Boot to GDM > 2. Click your username > 3. Type the wrong password a couple of times, pressing enter after each > time > 4. Type the right password > > If the bug is happening, after 4. the system hangs at a blank screen > with the mouse cursor. If you then switch to a VT or otherwise connect > to the machine, you can examine the journal and you'll see a > G_IS_DBUS_CONNECTION failure. > > [ Fix ] > > Marco and I worked upstream on this fix. We found out that there was a > problem like this- > > The GdmClient has a shared GDBusConnection for its operations. The > first time someone calls for it, it is created and stored in the > object's private structure. Subsequent calls return *a new reference* > to this same object. It turned out that the asynchronous method to get > the connection was accidentally unreferencing its object before giving > it to the caller if it was returning an already-existing connection. > > For this to work properly, we need to nullify the pointer we stored > when the connection goes away, so we know when to make a new one. > There were some cases where we didn't add the weak references required > to do that. Those are also fixed. > > [ Regression potential ] > > Now we share connections more than we did before. We also more > carefully track when to clear our object. If we got this wrong, we > might end up leaking the connection or dropping it in even more cases. > > [ Original report ] > > WORKAROUND: After typing an incorrect password, click Cancel, then > click your name, then enter your password again. > > --- > > Trying to log into my session (Gnome, Xorg), if I enter the wrong > password before entering it correctly, the session doesn't load and I > get a purple screen, a mouse cursor, and an invisible but clickable > menu in the top right. If I enter it correctly the first time, there > is no problem. > > I've replicated this from a fresh boot, after logging out and after > 'sudo service gdm restart' from the Ctrl-Alt-F4 console. > > This is a fresh
[Bug 981860] Re: [gm45] GPU lockup render.IPEHR: 0x01800020
*** This bug is a duplicate of bug 768184 *** https://bugs.launchpad.net/bugs/768184 This thing seems to appear when I leave the PC idle for a long time. Power saving options do not seem to affect like they are being set, but I really don't know very well what is the fact. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/981860 Title: [gm45] GPU lockup render.IPEHR: 0x01800020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/981860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387528] [NEW] package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2
Public bug reported: Sorry, not able to add much comment - this report is originated automatically I tried to install java support when I needed it in the middle of session in certain www site. As I was logged in to service requiring relatively demanding authentication using keys provided by a bank (not the bank site though). I tried to install java without logging out and without shutting down the browser (google chrome). I failed in every way and have not used the site ever since though... so right now I don't know my browser's current java support status . ProblemType: Package DistroRelease: Ubuntu 14.10 Package: icedtea-netx:amd64 1.5.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Wed Oct 29 11:52:51 2014 DuplicateSignature: package:icedtea-netx:amd64:1.5.1-1ubuntu1:aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2 ErrorMessage: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2 InstallationDate: Installed on 2014-10-25 (4 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: icedtea-web Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: icedtea-web (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387528 Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1387528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1387528] Re: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2
I tried to install it several times again after completely removing everything java related using instructions in http://askubuntu.com/questions/84483/how-to-completely-uninstall-java then tried to install icedtea from sw-center. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387528 Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1387528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1387528] Re: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2
Thanks for confirmation, I tried to install it several times afterward and got my system in problems when trying too hard - though luckily was able to remove and fix everything in the end. I believe it is good idea to make the package unavailable as ordinary users will get into troubles they can not solve easily. br Heikki 2014-11-01 15:49 GMT+02:00 Bob H <1387...@bugs.launchpad.net>: > you have not installed incorrectly > > there does appear to be a problem with icedtea-netx:amd64 1.5.1-1ubuntu1 > in the repositories at Utopic > > This means that icedtea-web cannot be installed on Utopic until it is > fixed > > java does work in Trusty Tahr as it does not use this package > > Ubuntu can either regress to the packages in Trusty or wait until Debian > produces a fix > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1387528 > > Title: > package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: > aliprosessi komentotiedosto post-installation asennettu palautti > virhetilakoodin 2 > > Status in “icedtea-web” package in Ubuntu: > Confirmed > > Bug description: > Sorry, not able to add much comment - this report is originated > automatically > > I tried to install java support when I needed it in the middle of > session in certain www site. As I was logged in to service requiring > relatively demanding authentication using keys provided by a bank (not > the bank site though). I tried to install java without logging out and > without shutting down the browser (google chrome). I failed in every > way and have not used the site ever since though... so right now I > don't know my browser's current java support status . > > ProblemType: Package > DistroRelease: Ubuntu 14.10 > Package: icedtea-netx:amd64 1.5.1-1ubuntu1 > ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 > Uname: Linux 3.16.0-24-generic x86_64 > ApportVersion: 2.14.7-0ubuntu8 > Architecture: amd64 > Date: Wed Oct 29 11:52:51 2014 > DuplicateSignature: > package:icedtea-netx:amd64:1.5.1-1ubuntu1:aliprosessi komentotiedosto > post-installation asennettu palautti virhetilakoodin 2 > ErrorMessage: aliprosessi komentotiedosto post-installation asennettu > palautti virhetilakoodin 2 > InstallationDate: Installed on 2014-10-25 (4 days ago) > InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 > (20141022.1) > SourcePackage: icedtea-web > Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to > install/upgrade: aliprosessi komentotiedosto post-installation asennettu > palautti virhetilakoodin 2 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1387528/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1387528 Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: aliprosessi komentotiedosto post-installation asennettu palautti virhetilakoodin 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icedtea-web/+bug/1387528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1363785] Re: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
We don't need java right now -> so no hurry for me with the fix or workaround. Thanks anyway to all. 2014-11-02 12:21 GMT+02:00 Paul Dooley <1363...@bugs.launchpad.net>: > Remember when using the workaround in post #14 to change "amd64" to > "i386" if you are using a 32-bit installation...did this and dependency > fixed (running an old P4 system!). > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1387528). > https://bugs.launchpad.net/bugs/1363785 > > Title: > package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: > subprocess installed post-installation script returned error exit > status 2 > > Status in Iced Tea: > New > Status in “icedtea-web” package in Ubuntu: > Triaged > Status in “icedtea-web” source package in Utopic: > Triaged > > Bug description: > Attempted to install icedtea-7-plugin on Ubuntu MATE Remix and > received this error. Looks like an upstream bug from the Ubuntu MATE > team, but seems to affect other users as well. Has been reported via > IRC on Freenode #ubuntu-mate as also existing in Ubuntu GNOME 14.04 > Trusty. > > ProblemType: Package > DistroRelease: Ubuntu 14.10 > Package: icedtea-netx:amd64 1.5.1-1ubuntu1 > ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 > Uname: Linux 3.16.0-11-generic x86_64 > ApportVersion: 2.14.7-0ubuntu1 > Architecture: amd64 > Date: Sun Aug 31 20:15:55 2014 > DuplicateSignature: package:icedtea-netx:amd64:1.5.1-1ubuntu1:subprocess > installed post-installation script returned error exit status 2 > ErrorMessage: subprocess installed post-installation script returned > error exit status 2 > InstallationDate: Installed on 2014-09-01 (0 days ago) > InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - pre-beta2.24117 > amd64 (20140829) > SourcePackage: icedtea-web > Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to > install/upgrade: subprocess installed post-installation script returned > error exit status 2 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/icedtea/+bug/1363785/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363785 Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/icedtea/+bug/1363785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1363785] Re: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
I am sorry, I fail to understand the discussion going on - have not been reading it too carefully though. Why this still continues? I think it is quite clear to development team that fix is needed and I am 100% certain they know how to proceed. It is just matter of prioritization, which brings me some desperate feelings as the focus seems to be now somewhere else and the hell is brought to your PC just by installing 14.10. Tue Nov 11 2014 at 4.25.46 Luis Alvarado <1363...@bugs.launchpad.net> kirjoitti: > No. This error appears simply by trying to install the icedtea-plugin. > That's all you need to do to get the error. > > 1. Install Ubuntu > 2. Update the repositories and try to install the icedtea-plugin. > 3. Welcome hell to your PC. > > This applies to the icedtea version 7.x which has the 1.5.1-1ubuntu1 > package version. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1387528). > https://bugs.launchpad.net/bugs/1363785 > > Title: > package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: > subprocess installed post-installation script returned error exit > status 2 > > Status in Iced Tea: > New > Status in NetBeans IDE: > New > Status in “icedtea-web” package in Ubuntu: > Triaged > Status in “icedtea-web” source package in Utopic: > Triaged > > Bug description: > Attempted to install icedtea-7-plugin on Ubuntu MATE Remix and > received this error. Looks like an upstream bug from the Ubuntu MATE > team, but seems to affect other users as well. Has been reported via > IRC on Freenode #ubuntu-mate as also existing in Ubuntu GNOME 14.04 > Trusty. > > ProblemType: Package > DistroRelease: Ubuntu 14.10 > Package: icedtea-netx:amd64 1.5.1-1ubuntu1 > ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 > Uname: Linux 3.16.0-11-generic x86_64 > ApportVersion: 2.14.7-0ubuntu1 > Architecture: amd64 > Date: Sun Aug 31 20:15:55 2014 > DuplicateSignature: package:icedtea-netx:amd64:1.5.1-1ubuntu1:subprocess > installed post-installation script returned error exit status 2 > ErrorMessage: subprocess installed post-installation script returned > error exit status 2 > InstallationDate: Installed on 2014-09-01 (0 days ago) > InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - pre-beta2.24117 > amd64 (20140829) > SourcePackage: icedtea-web > Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to > install/upgrade: subprocess installed post-installation script returned > error exit status 2 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/icedtea/+bug/1363785/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1363785 Title: package icedtea-netx:amd64 1.5.1-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/icedtea/+bug/1363785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
