[Bug 1481835]
*** Bug 122179 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481835 Title: [UPSTREAM] Unable to group raster image(s) with drawing object(s) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481835]
*** Bug 143417 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481835 Title: [UPSTREAM] Unable to group raster image(s) with drawing object(s) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481835]
*** Bug 152672 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481835 Title: [UPSTREAM] Unable to group raster image(s) with drawing object(s) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2036817]
*** Bug 157855 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2036817 Title: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->() To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729433]
Ben didn't provide version details in comment 55. Jeff, thank you for the follow-up, but because this report is about the barely visible, minuscule window issue, and because there's 60+ comments, let's see if your issue is already better described elsewhere, or if it needs a fresh start in a new report, with clear steps. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729433 Title: LibreOffice doesn't remember window size when running under Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949291]
(In reply to Heiko Tietze from comment #20) > (In reply to Stéphane Guillou (stragu) from comment #19) > > Heiko, are these delayed until the next opportunity, or are they just not > > shown at all? > Just delayed. GetInvolved will come first and Donate the next program start, > if no other infobar is shown. Great, thank you for clarifying! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949291 Title: LibreOffice has started displaying a donation nag To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949291]
(In reply to Heiko Tietze from comment #16) > The patch hides the Donate and GetInvolved infobar if another one is visible. Heiko, are these delayed until the next opportunity, or are they just not shown at all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949291 Title: LibreOffice has started displaying a donation nag To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1974093] [NEW] iwlwifi related BUG: kernel NULL pointer dereference, address: 0000000000000318
Public bug reported: This happened on 3 different laptops at approximately the same time. All laptops were connected to the same accesspoint SSID (WeWork). All laptops are Lenovo L15 Gen1 AMD laptops. All run Ubuntu 20.04.4. Packages are: linux-image-5.14.0-1036-oem5.14.0-1036.40 linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 After 30 minutes where multiple reboots were tried, the problem went away. 2 laptops are on 5.14.0-1036-oem, 1 is on 5.11.0-46-generic, all packaged as provided by Ubuntu. VirtualBox and AMDGPU are installed on all laptops concerned, but some of the crashes happened before they were loaded in the kernel. All reports were acquired from systemd-pstore, no other place had any information about the crash. laptop 1 on 5.14.0-1036-oem [ 11.205283] BUG: kernel NULL pointer dereference, address: 0318 [ 11.205289] #PF: supervisor read access in kernel mode [ 11.205291] #PF: error_code(0x) - not-present page [ 11.205292] PGD 0 P4D 0 [ 11.205294] Oops: [#1] SMP NOPTI [ 11.205296] CPU: 0 PID: 1242 Comm: irq/78-iwlwifi: Not tainted 5.14.0-1036-oem #40-Ubuntu [ 11.205299] Hardware name: LENOVO 20U7000VUS/20U7000VUS, BIOS R19ET28W (1.12 ) 08/12/2020 [ 11.205300] RIP: 0010:cfg80211_rx_unprot_mlme_mgmt+0x16/0x130 [cfg80211] [ 11.205333] Code: ff 0f 0b e9 8f fe ff ff e8 c7 2d b0 dd 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 08 <4c> 8b bf 18 03 00 00 49 8b 1f 48 85 db 0f 84 f6 00 00 00 49 89 d5 [ 11.205335] RSP: 0018:bc6040003a50 EFLAGS: 00010286 [ 11.205336] RAX: 6d7e RBX: bc6040003c30 RCX: 0080 [ 11.205338] RDX: 00df RSI: 9b5145936000 RDI: [ 11.205339] RBP: bc6040003a80 R08: 9b5145936000 R09: 9b51582873a8 [ 11.205340] R10: R11: R12: 9b514c613c00 [ 11.205341] R13: R14: 0001 R15: 0080 [ 11.205342] FS: () GS:9b582f60() knlGS: [ 11.205343] CS: 0010 DS: ES: CR0: 80050033 [ 11.205344] CR2: 0318 CR3: 000116bc CR4: 00350ef0 [ 11.205345] Call Trace: [ 11.205347] [ 11.205352] ieee80211_rx_h_decrypt+0x559/0x5c0 [mac80211] [ 11.205384] ? ieee80211_rx_handlers_result+0x97/0x210 [mac80211] [ 11.205403] ieee80211_rx_handlers+0x373/0x1200 [mac80211] [ 11.205422] ieee80211_invoke_rx_handlers+0xf0/0x700 [mac80211] [ 11.205440] ieee80211_prepare_and_rx_handle+0x1d7/0x3a0 [mac80211] [ 11.205460] ? ieee80211_scan_rx+0xf9/0x160 [mac80211] [ 11.205494] ieee80211_rx_list+0x25d/0x5f0 [mac80211] [ 11.205527] ieee80211_rx_napi+0x38/0xa0 [mac80211] [ 11.205561] iwl_mvm_rx_mpdu_mq+0xd20/0x1470 [iwlmvm] [ 11.205575] iwl_mvm_rx_mq+0x4f/0xb0 [iwlmvm] [ 11.205586] iwl_pcie_rx_handle_rb.constprop.0+0x211/0x470 [iwlwifi] [ 11.205598] iwl_pcie_rx_handle+0x201/0x4f0 [iwlwifi] [ 11.205609] iwl_pcie_napi_poll_msix+0x2c/0xd0 [iwlwifi] [ 11.205619] __napi_poll+0x31/0x140 [ 11.205624] net_rx_action+0x23f/0x290 [ 11.205626] __do_softirq+0xcf/0x275 [ 11.205630] ? irq_finalize_oneshot.part.0+0xf0/0xf0 [ 11.205633] do_softirq+0x66/0x80 [ 11.205635] [ 11.205636] [ 11.205637] __local_bh_enable_ip+0x50/0x60 [ 11.205638] iwl_pcie_irq_rx_msix_handler+0xce/0x180 [iwlwifi] [ 11.205647] irq_thread_fn+0x28/0x60 [ 11.205648] irq_thread+0xcb/0x160 [ 11.205650] ? irq_forced_thread_fn+0x90/0x90 [ 11.205651] ? irq_thread_check_affinity+0xf0/0xf0 [ 11.205653] kthread+0x12a/0x150 [ 11.205655] ? set_kthread_struct+0x40/0x40 [ 11.205656] ret_from_fork+0x22/0x30 [ 11.205660] [ 11.205661] Modules linked in: cmac algif_hash algif_skcipher af_alg overlay bnep nls_iso8859_1 intel_rapl_msr intel_rapl_common iwlmvm uvcvideo snd_ctl_led edac_mce_amd r8153_ecm mac80211 videobuf2_vmalloc snd_hda_codec_realtek cdc_ether btusb videobuf2_memops videobuf2_v4l2 snd_hda_codec_generic usbnet btrtl btbcm libarc4 kvm_amd snd_hda_codec_hdmi r8152 videobuf2_common snd_usb_audio btintel kvm snd_usbmidi_lib snd_hda_intel joydev snd_seq_midi snd_intel_dspcfg bluetooth snd_seq_midi_event snd_intel_sdw_acpi input_leds videodev thinkpad_acpi mii snd_rawmidi rapl iwlwifi snd_hda_codec nvram think_lmi(+) ecdh_generic platform_profile mc snd_hda_core ecc firmware_attributes_class efi_pstore wmi_bmof serio_raw k10temp ledtrig_audio snd_seq snd_hwdep snd_pci_acp6x snd_rn_pci_acp3x cfg80211 snd_pcm snd_pci_acp3x snd_seq_device ccp snd_timer snd ucsi_acpi typec_ucsi soundcore typec mac_hid sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables autofs4 [ 11.205702] dm_crypt uas usb_storage hid_generic usbhid hid amdgpu rtsx_pci_sdmmc iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt
[Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)
Hello, I installed the 5.11.0-27 but still no sound. Let's says the kernel is good, are there any settings involved ? Like kernel startup parameter or any other ones ? Linux XPS-17-9700 5.11.0-27-generic #29~20.04.1-Ubuntu SMP Wed Aug 11 15:58:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912673 Title: sounds not working on Dell XPS 17 (9700) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)
Hello, can you explain how to install this kernel 5.11.0-19 ? thanks ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912673 Title: sounds not working on Dell XPS 17 (9700) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880683] Re: unable to load mod_vroot.c
This bug just affected me. Had to hand compile mod_vroot using the proftpd 1.3.6c sources -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880683 Title: unable to load mod_vroot.c To manage notifications about this bug go to: https://bugs.launchpad.net/proftpd-dfsg/+bug/1880683/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930393] Re: any local user can shut clamd down via control socket
> Hello Stephane, maybe joining the amavisd-new user's to the clamav group would be a simpler way around the stricter socket permissions you are proposing? Hi Simon, No, as I said in comment #4, that doesn't work as amavisd-new doesn't set supplementary IDs, just does a setuid() and setgid() with the configured user and group. Also we don't want to give it access to all of clamav's restricted resources (mailbox, logs...), only the socket (which we'd only restrict here to mitigate this vulnerability). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930393 Title: any local user can shut clamd down via control socket To manage notifications about this bug go to: https://bugs.launchpad.net/clamav/+bug/1930393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930393] Re: any local user can shut clamd down via control socket
> I suggest proposing your patch in a Debian bug to get the maintainer's feedback on it. I've now raised https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989549 Should we carry on discussion over there? ** Bug watch added: Debian Bug tracker #989549 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989549 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930393 Title: any local user can shut clamd down via control socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1930393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930393] Re: any local user can shut clamd down via control socket
>From systemd.service(5): > Type= > Configures the process start-up type for this service unit. > One of simple, exec, forking, oneshot, dbus, notify or > idle: > > • If set to simple (the default if ExecStart= is > specified but neither Type= nor BusName= are), the > service manager will consider the unit started > immediately after the main service process has been > forked off. [...] > • If set to forking, it is expected that the process > configured with ExecStart= will call fork() as part of > its start-up. The parent process is expected to exit > when start-up is complete and all communication > channels are set up. The child continues to run as the > main service process, and the service manager will > consider the unit started when the parent process > exits. This is the behavior of traditional UNIX > services. If this setting is used, it is recommended to > also use the PIDFile= option, so that systemd can > reliably identify the main process of the service. > systemd will proceed with starting follow-up units as > soon as the parent process exits. So as long as the parent doesn't exit before the service is ready to accept connections, it should be reliable. It seems to be the case here. Note that clamd can take quite a long time to start (hence the 7 minute timeout which btw I don't think makes sense with type=simple and --foreground), which might be why type=forking was abandoned? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930393 Title: any local user can shut clamd down via control socket To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1930393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Thanks. I notice your first write() is on fd 3 while the 2nd is on stdout (while for me the first 2 are on fd 3, which in my case is the LDAPS socket). For the issue to be reproduced, we need the client to be paused after having send the TLS "client hello". The first time the breakpoint is hit, you should be seeing something like: ``` #0 __GI___libc_write (fd=3, buf=0x55ace4ab, nbytes=75) at ../sysdeps/unix/sysv/linux/write.c:27 #1 0x7797b408 in sb_debug_write (sbiod=0x55ab4810, buf=0x55ace4ab, len=75) at ../../../../libraries/liblber/sockbuf.c:854 #2 0x76bd5a0a in _gnutls_writev_emu (fd=fd@entry=0x5578f240, giovec=giovec@entry=0x7fff9b90, giovec_cnt=giovec_cnt@entry=3, vec=0, session=, session=) at buffers.c:447 #3 0x76bd608c in _gnutls_writev (total=126, giovec_cnt=3, giovec=0x7fff9b90, session=0x5578d3d0) at buffers.c:504 #4 _gnutls_io_write_flush (session=session@entry=0x5578d3d0) at buffers.c:698 #5 0x76bd7200 in _gnutls_handshake_io_write_flush (session=session@entry=0x5578d3d0) at buffers.c:820 #6 0x76bd9348 in _gnutls_send_handshake (session=session@entry=0x5578d3d0, bufel=bufel@entry=0x55acd620, type=type@entry=GNUTLS_HANDSHAKE_FINISHED) at handshake.c:1335 #7 0x76bda4ed in _gnutls_send_finished (again=, session=0x5578d3d0) at handshake.c:763 #8 send_handshake_final (session=session@entry=0x5578d3d0, init=init@entry=1) at handshake.c:3098 #9 0x76bdcd29 in handshake_client (session=0x5578d3d0) at handshake.c:2946 #10 gnutls_handshake (session=0x5578d3d0) at handshake.c:2626 #11 0x77bbb183 in tlsg_session_accept (session=0x55abb070) at tls_g.c:361 #12 0x77bb8751 in ldap_int_tls_connect (ld=ld@entry=0x557890d0, conn=) at tls2.c:362 #13 0x77bb9466 in ldap_int_tls_start (ld=ld@entry=0x557890d0, conn=conn@entry=0x55789500, srv=srv@entry=0x55789440) at tls2.c:860 #14 0x77b912b6 in ldap_int_open_connection (ld=ld@entry=0x557890d0, conn=conn@entry=0x55789500, srv=0x55789440, async=async@entry=0) at open.c:448 #15 0x77ba634d in ldap_new_connection (ld=ld@entry=0x557890d0, srvlist=srvlist@entry=0x55789198, use_ldsb=use_ldsb@entry=1, connect=connect@entry=1, bind=bind@entry=0x0, m_req=m_req@entry=0, m_res=0) at request.c:487 #16 0x77b9074a in ldap_open_defconn (ld=ld@entry=0x557890d0) at open.c:41 #17 0x77ba7908 in ldap_send_initial_request (ld=ld@entry=0x557890d0, msgtype=msgtype@entry=96, dn=dn@entry=0x0, ber=0x557894a0, msgid=1) at request.c:130 #18 0x77b9ab8f in ldap_sasl_bind (ld=0x557890d0, dn=0x0, mechanism=, cred=0x557692e0 , sctrls=0x0, cctrls=0x0, msgidp=0x7fffa2dc) at sasl.c:164 #19 0xd33b in ?? () #20 0x844f in ?? () #21 0x77388bf7 in __libc_start_main (main=0x81b0, argc=4, argv=0x7fffe638, init=, fini=, rtld_fini=, stack_end=0x7fffe628) at ../csu/libc-start.c:310 #22 0x966a in ?? () ``` And we need to make sure the server or client doesn't reject that connection outright. It would worth running "tshark -i any -f 'port 636'" in the mean time to verify the "client hello" is sent and that the server is willing to carry on the connection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
lincvz: > Thank you for the patch and your investigations. In the next few days, I > cannot install the patched package on my production machines. I'll let you > know when I can. Thanks. Can you reproduce a similar issue with the modus operandi (using gdb) I describe above? (Note that while it renders slapd unresponsive, service is restored as soon as you quit or detach gdb on the client). If you do, it would be worth getting a backtrace on the slapd threads again, so see if you get the same ones as before or some similar to mine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
> This is a valid issue, but are we certain it's the same one? The > reporter talked about sched_yield and their backtraces included several > threads of back_monitor waiting on some kind of lock. You're right. It may be a different issue (though possibly linked to the same root cause). In my case, all other threads are stuck on: #0 0x7f2a010fdad3 in futex_wait_cancelable (private=, expected=0, futex_word=0x55d92cadaa78) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x55d92cadaa28, cond=0x55d92cadaa50) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=cond@entry=0x55d92cadaa50, mutex=mutex@entry=0x55d92cadaa28) at pthread_cond_wait.c:655 #3 0x7f2a01fc7475 in ldap_pvt_thread_cond_wait (cond=cond@entry=0x55d92cadaa50, mutex=mutex@entry=0x55d92cadaa28) at ../../../../libraries/libldap_r/thr_posix.c:277 #4 0x7f2a01fc6d1b in ldap_int_thread_pool_wrapper (xpool=0x55d92cadaa20) at ../../../../libraries/libldap_r/tpool.c:683 #5 0x7f2a010f76db in start_thread (arg=0x7f29f99b6700) at pthread_create.c:463 #6 0x7f2a00e1971f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
> It can be reproduced by running on a client: > > gdb --args ldapsearch -H ldaps://ldap.example.com -x > > Then in gdb: > > break write > run > continue I can no longer reproduce it after I rebuild and install the libldap package with https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e applied. Note that since the above is enough to render slapd unresponsive for 15 minutes, it could be considered as a serious DoS vulnerability. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Yes, https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503 can't be directly applied there. There have been other changes in between in that section including changes in API, so it would take more effort to backport that fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
cherry picking https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e should fix this particular issue but reintroduce https://bugs.openldap.org/show_bug.cgi?id=8650. It may be necessary to pick https://github.com/openldap/openldap/commit/735e1ab14bb055344b4e767a216aa410aa7d1503 as well but as that's much more recent, I can't tell if it's valid on top of the package used in bionic. I'm going to do some tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
The important backtrace in there is the one from thread 11: #0 0x7fb288428474 in read () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #1 0x7fb2890c4518 in ?? () from /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 No symbol table info available. #2 0x7fb287895848 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #3 0x7fb28788f96a in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #4 0x7fb287896d03 in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #5 0x7fb28789991c in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #6 0x7fb2878a10cb in ?? () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #7 0x7fb28789d572 in gnutls_handshake () from /usr/lib/x86_64-linux-gnu/libgnutls.so.30 No symbol table info available. #8 0x7fb289304199 in ?? () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 No symbol table info available. #9 0x7fb289301abb in ldap_pvt_tls_accept () from /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 No symbol table info available. #10 0x556b843e6f69 in connection_read (cri=, s=430) at ../../../../servers/slapd/connection.c:1375 debug symbols are missing there, but I have the exact same problem and get: #0 0x7f2a01101474 in __libc_read (fd=40, buf=0x7f29dc142ecb, nbytes=5) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f2a01db0518 in sb_debug_read (sbiod=0x7f29dc10e940, buf=0x7f29dc142ecb, len=5) at ../../../../libraries/liblber/sockbuf.c:829 #2 0x7f2a00558848 in _gnutls_stream_read (ms=0x7f29e8ffb41c, pull_func=0x7f2a01ff1da0 , size=5, bufel=, session=0x7f29dc008060) at buffers.c:344 #3 _gnutls_read (ms=0x7f29e8ffb41c, pull_func=0x7f2a01ff1da0 , size=5, bufel=, session=0x7f29dc008060) at buffers.c:424 #4 _gnutls_io_read_buffered (session=session@entry=0x7f29dc008060, total=5, recv_type=recv_type@entry=4294967295, ms=0x7f29e8ffb41c) at buffers.c:579 #5 0x7f2a0055296a in recv_headers (ms=, record=0x7f29e8ffb470, htype=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, type=GNUTLS_HANDSHAKE, record_params=0x7f29dc1279f0, session=0x7f29dc008060) at record.c:1045 #6 _gnutls_recv_in_buffers (session=session@entry=0x7f29dc008060, type=type@entry=GNUTLS_HANDSHAKE, htype=htype@entry=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, ms=, ms@entry=0) at record.c:1173 #7 0x7f2a00559d03 in _gnutls_handshake_io_recv_int (session=session@entry=0x7f29dc008060, htype=htype@entry=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, hsk=hsk@entry=0x7f29e8ffb580, optional=optional@entry=0) at buffers.c:1412 #8 0x7f2a0055c91c in _gnutls_recv_handshake (session=session@entry=0x7f29dc008060, type=type@entry=GNUTLS_HANDSHAKE_CLIENT_KEY_EXCHANGE, optional=optional@entry=0, buf=buf@entry=0x7f29e8ffb830) at handshake.c:1465 #9 0x7f2a005640cb in _gnutls_recv_client_kx_message (session=session@entry=0x7f29dc008060) at kx.c:563 #10 0x7f2a00560572 in handshake_server (session=0x7f29dc008060) at handshake.c:3327 #11 gnutls_handshake (session=0x7f29dc008060) at handshake.c:2629 #12 0x7f2a01ff2199 in tlsg_session_accept (session=0x7f29dc1133f0) at tls_g.c:363 #13 0x7f2a01fefabb in ldap_pvt_tls_accept (sb=0x7f299c0051a0, ctx_arg=0x55d92cbca560) at tls2.c:425 and I've tracked it down to: https://bugs.openldap.org/show_bug.cgi?id=8650#c12 Basically, what we see is one thread stuck in a busy loop doing read()s on the TCP socket which all return immediately with EAGAIN as the fd is in non-blocking mode. In my cases, the client go offline just after sending the TLS client hello. That lasts for 15 minutes or about, probably until some timeout after which the TCP connection is eventually considered dead. It can be reproduced by running on a client: gdb --args ldapsearch -H ldaps://ldap.example.com -x Then in gdb: break write run continue Then the client is paused after sending the TLS "client hello". https://bugs.openldap.org/show_bug.cgi?id=8650#c12 explains that it's https://github.com/openldap/openldap/commit/7b5181da8cdd47a13041f9ee36fa9590a0fa6e48 that is responsible for the issue. https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e reverted that commit, but that one did not make it into bionic. So cherry picking https://github.com/openldap/openldap/commit/4c1ab16ade18a253dd81df7e6eced4d920ac6a8e should fix it. ** Bug watch added: bugs.openldap.org/ #8650 https://bugs.openldap.org/show_bug.cgi?id=8650 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1921508] [NEW] package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1867678 *** https://bugs.launchpad.net/bugs/1867678 Public bug reported: During dist upgrade from ubuntu 19.10 to 20.10 (do-release-upgrade) on hyper-v: Processing triggers for dbus (1.12.16-2ubuntu2.1) ... Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-3ubuntu0.2) ... Processing triggers for rygel (0.38.3-1ubuntu1) ... Processing triggers for sgml-base (1.29.1) ... Errors were encountered while processing: xrdp Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xrdp 0.9.12-1 ProcVersionSignature: Ubuntu 5.3.0-64.58-generic 5.3.18 Uname: Linux 5.3.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 26 12:22:24 2021 DuplicateSignature: package:xrdp:0.9.12-1 Installing new version of config file /etc/xrdp/xrdp_keyboard.ini ... ln: failed to create symbolic link '/etc/xrdp/cert.pem': File exists dpkg: error processing package xrdp (--configure): installed xrdp package post-installation script subprocess returned error exit status 1 ErrorMessage: installed xrdp package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: xrdp Title: package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2021-03-26 (0 days ago) mtime.conffile..etc.xrdp.sesman.ini: 2019-09-05T17:58:04.857929 mtime.conffile..etc.xrdp.xrdp.ini: 2019-09-05T17:58:04.853930 ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921508 Title: package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1921508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 243578]
I can reproduce with Thunderbird 78.8.0 on Debian. IMAP, IMAPS, SMTPS connections go via the configured SOCKS5 proxy, but LDAPS connections are not proxied. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/243578 Title: Thunderbird address book won't use socks to access ldap server To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/243578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849416]
Thanks @MarkusKuhn for taking care of explaining. I understand that it is vexing when users complain about a problem caused by a bug in a third party program. Still, thunderbird not displaying any hint feels wrong. I'm also aware that https://en.wikipedia.org/wiki/Robustness_principle can sometimes hurt. I guess the question can only be resolved pragmatically, like "Do we have the power to force Microsoft Exchange to fix that?", "Does implementing the wish cause costs, like extra code complexity?" or "What happen if we refuse to do anything about this problem experiences by users?". Anyway, thanks again Markus for enlightening us. > Don't use Microsoft Exchange if what you really want is proper RFC822+MIME email. It never was. Spread the word. I'm already self-hosted and since the hosting company of my freelancing activity switched to MS Exchange I'm considering to self-host that, too, for what it's worth. > Repeat: this is a feature request for a workaround of a long-standing > Microsoft Exchange bug. This is not a Thunderbird bug. I'm willing to change the field "Type: defect" to " Type: feature request" but Bugzilla does not let me do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849416 Title: text/calendar attachments are not shown at all To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/849416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 849416]
Same as Daniel here. I experienced this bug on Linux. Can reproduce it now by displaying sample e-mail from comment 4 ( https://bugzilla.mozilla.org/show_bug.cgi?id=505024#c4 ) on 68.10.0 (64 bits). In my case I received automatic invitation e-mails which did not have any text, just the calendar entry. They appeared as totally blank e-mail, only showing the e-mail source code allowed me to realize there was a calendar entry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/849416 Title: text/calendar attachments are not shown at all To manage notifications about this bug go to: https://bugs.launchpad.net/seamonkey/+bug/849416/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
I have one instance that kernel panicked when it updated to 0.11-4ubuntu2.6 using auto updates. However I cannot confirm that I actually rebooted that instance after installing 0.11-4ubuntu2.5 So far none of my other instances panicked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871044] Re: remmina crashed with SIGSEGV in g_type_check_instance_cast()
Update 07 Apr 2020 : Remmina v1.4.1 from Ubuntu 20.04 beta package still bugs at connection. But, I have tried with Reminna Snap v1.4.1 (git 9fada695) and it works very well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871044 Title: remmina crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1871044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503]
Definitive fix under review @ https://codereview.scilab.org/#/c/21179/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503]
(In reply to Paul van Haren from comment #18)
> Dear Stephane,
>
> I think you're overlooking the observation by Nikolay (close to the bottom of
> comment 11):
>
> # Brief analysis
>
> I believe that root cause of the problem is change of `hid_t` datatype in HDF
> library.
>
> It is not an `int` anymore, it is `int64_t`.
> But the scilab source code have many places with hardcoded `int`.
> See for example `openHDF5File` -
> http://cgit.scilab.org/scilab/tree/scilab/modules/hdf5/src/c/h5_fileManagement.c
> which calls `H5Fopen`:
>
> ```
> int openHDF5File(const char *name, int _iAppendMode)
> {
> hid_t file;
> ...
>
> file = H5Fopen(filename, H5F_ACC_RDONLY, H5P_DEFAULT);
> ...
> return file;
> }
> ```
> Best regards, Paul
I have understood the problem and one of the possible fixes is to
redefine hid_t to int (as in the link I gave) as hdf5 1.10 seems to
accept it. But I don't understand the logic of Nikolay's patch. I see
for example
-hid_t iFile = openHDF5File(filename.data(), 0);
+int iFile = openHDF5File(filename.data(), 0);
In the piece of code your gave, the logic would be to define the output
type of openHDF5File as hid_t. If you declare the "file" id as an int
the destructive conversion will occur in the call "file = H5Fopen..."
since H5Fopen() yields an hid_t. So instead of changing type in the
(many) calls it is simpler to change the output type of the function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765503
Title:
scilab: save, open and ATOMS system is broken in Scilab 6 on bionic,
cosmic, disco and eoan
To manage notifications about this bug go to:
https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503]
*** Bug 16287 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503]
(In reply to Paul van Haren from comment #15) > As per the analysis of Nikolay, the impact of this bug means that ATOMS and > many other functions are not available to Ubuntu users. > > I've tried installing the latest successful nightly build, but that doesn't > work as the customization for Ubuntu/Debian is missing and too many > environment issues arose. E.g. when starting scilab from the command line, > nothing happens, no output, no CPU load. The only think you can do is > stop the process (^Z) and then kill the stopped job. I couldn't run the > stable 6.0.2. version either. > > Next, I've tried building from source, but here I couldn't get past the JOGL > and javah issue, also reported by Nikolay (the javah issue I could > work around, but I couldn't find a fix for the JOGL issue). > > Effectively, this means that I don't have means to run Scilab, and I guess > with me also most of the other Ubuntu/Debian users. > > @Stepahne, is there something you can do to raise the awareness on this issue > and take measures for a big fix release being pushed to the Ubuntu > package maintainers? > > Thanks and regards, Paul If think there is a simpler fix than patching all relevant files: https://github.com/HDFGroup/HDF.PInvoke/wiki/Important-Differences- between-HDF5-1.8-and-1.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503]
(In reply to Paul van Haren from comment #15) > As per the analysis of Nikolay, the impact of this bug means that ATOMS and > many other functions are not available to Ubuntu users. > > I've tried installing the latest successful nightly build, but that doesn't > work as the customization for Ubuntu/Debian is missing and too many > environment issues arose. E.g. when starting scilab from the command line, > nothing happens, no output, no CPU load. The only think you can do is > stop the process (^Z) and then kill the stopped job. I couldn't run the > stable 6.0.2. version either. > > Next, I've tried building from source, but here I couldn't get past the JOGL > and javah issue, also reported by Nikolay (the javah issue I could > work around, but I couldn't find a fix for the JOGL issue). > > Effectively, this means that I don't have means to run Scilab, and I guess > with me also most of the other Ubuntu/Debian users. > > @Stepahne, is there something you can do to raise the awareness on this issue > and take measures for a big fix release being pushed to the Ubuntu > package maintainers? > > Thanks and regards, Paul If think there is a simpler fix than patching all relevant files: https://github.com/HDFGroup/HDF.PInvoke/wiki/Important-Differences-between-HDF5-1.8-and-1.10(In reply to Stéphane MOTTELET from comment #16) > (In reply to Paul van Haren from comment #15) > > As per the analysis of Nikolay, the impact of this bug means that ATOMS and > > many other functions are not available to Ubuntu users. > > > > I've tried installing the latest successful nightly build, but that doesn't > > work as the customization for Ubuntu/Debian is missing and too many > > environment issues arose. E.g. when starting scilab from the command line, > > nothing happens, no output, no CPU load. The only think you can do is > > stop the process (^Z) and then kill the stopped job. I couldn't run the > > stable 6.0.2. version either. > > > > Next, I've tried building from source, but here I couldn't get past the > > JOGL and javah issue, also reported by Nikolay (the javah issue I could > > work around, but I couldn't find a fix for the JOGL issue). > > > > Effectively, this means that I don't have means to run Scilab, and I guess > > with me also most of the other Ubuntu/Debian users. > > > > @Stepahne, is there something you can do to raise the awareness on this > > issue and take measures for a big fix release being pushed to the Ubuntu > > package maintainers? > > > > Thanks and regards, Paul > > If think there is a simpler fix than patching all relevant files: > > https://github.com/HDFGroup/HDF.PInvoke/wiki/Important-Differences-between-HDF5-1.8-and-1.10 I mean, something similar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765503]
Nikolay why don't you commit you patches on CR ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765503 Title: scilab: save, open and ATOMS system is broken in Scilab 6 on bionic, cosmic, disco and eoan To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1765503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842669] [NEW] pure-ftpd needs update to at least v1.0.47-3 in 18.04 LTS !
Public bug reported: 18.04 LTS still uses v1.0.46 version of pure-ftpd. This version is incompatible with recent versions of the popular FileZilla client due to TLS 1.3 handling issues in pure-ftpd when connection using secure FTPES. 18.04 LTS pure-ftpd is thus broken for any clients using up-to-date versions of this popular FTP client, which is critical for an LTS release ! 19.04 already uses v1.0.47 version of pure-ftpd; however, it is not an LTS release. Please quickly update pure-ftpd package to v1.0.47-3 or better !!! ** Affects: pure-ftpd (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/1842669 Title: pure-ftpd needs update to at least v1.0.47-3 in 18.04 LTS ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1842669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1292041] Re: Lockscreen doesn't turn off the screen
I have also been hit by this bug. Extremely irritating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
I confirm the issue in 19.04. I just upgraded from 16.04. I used to get in fine on eduroam not anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
See with just running ldapsearch after upgrade to 16.04: ``` # repeat 10 ldapsearch -x > /dev/null # tail /var/log/auth.log Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free Apr 19 14:53:01 hostname ldapsearch: DIGEST-MD5 common mech free ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/827151 Title: Annoying log message "DIGEST-MD5 common mech free" To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778800] Re: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post-installation script subprocess returned error exit status 1
This actually caused downtime for me today because of the apache update. The process stops apache, tries to stop u-u then exits, leaving apache down. When can we expect the fix to be released for xenial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778800 Title: package unattended-upgrades 1.1ubuntu1.18.04.1 failed to install/upgrade: installed unattended-upgrades package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1778800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793341] Re: Please Update kmymoney package
Major issues appearing when importing qif files have been solved recently https://bugs.kde.org/show_bug.cgi?id=397824 https://bugs.kde.org/show_bug.cgi?id=403565 Also, a couple of major bugs, leading to crashes of the package have been solved, incl: https://bugs.kde.org/show_bug.cgi?id=402750 Last, a bug in anonymous file creation, limiting its use: https://bugs.kde.org/show_bug.cgi?id=340902 ** Bug watch added: KDE Bug Tracking System #397824 https://bugs.kde.org/show_bug.cgi?id=397824 ** Bug watch added: KDE Bug Tracking System #403565 https://bugs.kde.org/show_bug.cgi?id=403565 ** Bug watch added: KDE Bug Tracking System #402750 https://bugs.kde.org/show_bug.cgi?id=402750 ** Bug watch added: KDE Bug Tracking System #340902 https://bugs.kde.org/show_bug.cgi?id=340902 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793341 Title: Please Update kmymoney package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmymoney/+bug/1793341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163406] Re: Device-mapper initialized before hardware-raid during system boot
If you are finding this bug and having an issue after upgrading to 16.04 and keeping upstart, see Bug #1573982 for a fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163406 Title: Device-mapper initialized before hardware-raid during system boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1163406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807043] Re: when rewriting sources.list ubuntu-release-upgrader doesn't check to see if new release is available
That fix breaks the upgrade (in my case from xenial to bionic) for users that use a local mirror over HTTPS as the _sourcesListEntryDownloadable->url_downloadable doesn't support HTTPS. It comments out the entries and adds: 2019-02-19 15:13:51,808 DEBUG entry '# deb https://localmirror.example.com/example/security.ubuntu.com/ubuntu xenial-security multiverse' was disabled (no Release file) The "Release file" is there but "url_downloadable" failed to download it because of the "https" scheme (note: the apt-transport-https package is installed). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807043 Title: when rewriting sources.list ubuntu-release-upgrader doesn't check to see if new release is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1807043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815021] Re: Can't read and write simultaneously from serial port
Probably same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813873 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815021 Title: Can't read and write simultaneously from serial port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1815021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815021] Re: Can't read and write simultaneously from serial port
``` $ bash -c 'sleep 1 && : < /dev/tty & read var' < /dev/tty bash: line 0: read: read error: 0: Resource temporarily unavailable ``` seems to be related and is possibly the same bug. See https://unix.stackexchange.com/questions/499422/bash-how-can-i-run- sudo-n-true-in-the-background-without-interfering- with-r/499433?noredirect=1#comment919635_499433 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815021 Title: Can't read and write simultaneously from serial port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1815021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807510] [NEW] package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: i have no detail sorry ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libssh-4:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 2 10:56:15 2018 DpkgHistoryLog: Start-Date: 2018-12-02 10:56:11 Commandline: /usr/bin/unattended-upgrade Upgrade: libssh-4:amd64 (0.8.0~20170825.94fa1e38-1ubuntu0.1, 0.8.0~20170825.94fa1e38-1ubuntu0.2) ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2018-11-04 (34 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807510 Title: package libglib2.0-dev-bin 2.56.3-0ubuntu0.18.04.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1807510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711916] Re: amule crashed with SIGSEGV in wxWindow::DoClientToScreen()
Still crashes with Ubuntu 18.10 beta (12 oct 2018) // amule 1:2.3.2-3build1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711916 Title: amule crashed with SIGSEGV in wxWindow::DoClientToScreen() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amule/+bug/1711916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I do not know Linux kernel process, but i would like to know if and when this fix will appear by defautl into Ubuntu doing a sudo apt upgrade ? Thanks and sorry for such basic question. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
I was just hit again with it today, with metacity 1:3.18.7-0ubuntu0.3 on 16.04. Here is the crash dump. ** Attachment added: "_usr_bin_metacity.1000.crash" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+attachment/5189891/+files/_usr_bin_metacity.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913323] Re: Occasional login failure and artefacts
Hello, same problem today, and same message appears in syslog: Jun 13 13:44:13 dlt0001ptrstp lightdm[1201]: ** (lightdm:1201): WARNING **: Error using VT_WAITACTIVE 7 on /dev/tty0: Interrupted system call Jun 13 13:44:13 dlt0001ptrstp org.gtk.vfs.Daemon[14134]: A connection to the bus can't be made Jun 13 13:44:13 dlt0001ptrstp org.a11y.atspi.Registry[14143]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Jun 13 13:44:13 dlt0001ptrstp org.a11y.atspi.Registry[14143]: after 37 requests (37 known processed) with 0 events remaining. Jun 13 13:44:14 dlt0001ptrstp systemd[1]: Started Session c7 of user lightdm. Jun 13 13:44:14 dlt0001ptrstp org.a11y.atspi.Registry[14660]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry Jun 13 13:44:31 dlt0001ptrstp org.gtk.vfs.Daemon[14651]: A connection to the bus can't be made I had to enter the password twice. Regards, -- Stephane Peters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913323 Title: Occasional login failure and artefacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/913323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913323] Re: Occasional login failure and artefacts
** Changed in: lightdm (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913323 Title: Occasional login failure and artefacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/913323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 913323] Re: Occasional login failure and artefacts
966: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch [+1635058.32s] DEBUG: DisplayServer x-1: Waiting for ready signal from X server :1 [+1635058.95s] DEBUG: Got signal 10 from process 7966 [+1635058.95s] DEBUG: DisplayServer x-1: Got signal from X server :1 [+1635058.95s] DEBUG: DisplayServer x-1: Connecting to XServer :1 [+1635059.00s] DEBUG: Seat seat0: Display server ready, starting session authentication [+1635059.00s] DEBUG: Session pid=7974: Started with service 'lightdm-greeter', username 'lightdm' [+1635059.02s] DEBUG: Session pid=7974: Authentication complete with return value 0: Success [+1635059.02s] DEBUG: Seat seat0: Session authenticated, running command [+1635059.02s] DEBUG: Session pid=7974: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter [+1635059.02s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+1635059.02s] DEBUG: Session pid=7974: Logging to /var/log/lightdm/seat0-greeter.log [+1635059.05s] DEBUG: Activating VT 8 ... [+1635070.71s] DEBUG: Authenticate result for user : Success [+1635070.71s] DEBUG: User authorized [+1635070.71s] DEBUG: Greeter sets language fr_FR [+1635070.76s] DEBUG: Greeter requests session xubuntu [+1635070.76s] DEBUG: Seat seat0: Returning to existing user session [+1635070.76s] DEBUG: Unlocking login1 session c24 [+1635070.77s] DEBUG: Activating VT 7 [+1635070.98s] DEBUG: Seat seat0: Stopping greeter [+1635070.98s] DEBUG: Session pid=8067: Sending SIGTERM [+1635070.98s] DEBUG: Activating login1 session c24 [+1635070.99s] DEBUG: Session pid=8146: Exited with return value 0 [+1635070.99s] DEBUG: Seat seat0: Session stopped [+1635070.99s] DEBUG: Seat seat0 changes active session to c24 [+1635070.99s] DEBUG: Session c24 is already active [+1635070.99s] DEBUG: Session pid=8067: Exited with return value 0 [+1635070.99s] DEBUG: Seat seat0: Session stopped [+1635070.99s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+1635070.99s] DEBUG: Sending signal 15 to process 8059 [+1635071.03s] DEBUG: Process 8059 exited with return value 0 [+1635071.03s] DEBUG: DisplayServer x-1: X server stopped [+1635071.03s] DEBUG: Releasing VT 8 [+1635071.03s] DEBUG: DisplayServer x-1: Removing X server authority /var/run/lightdm/root/:1 [+1635071.03s] DEBUG: Seat seat0: Display server stopped # /var/log/lightdm/seat0-greeter.log : indicator-application killed by TERM / process indicator-application stopped with state 1 ** (lightdm-gtk-greeter:23412): WARNING **: [PIDs] Failed to terminate process #23414: Aucun processus de ce type upstart: Le processus indicator-application main (23461) a été tué par le signal TERM ** Message: Starting lightdm-gtk-greeter 2.0.1 (Apr 11 2016, 06:05:31) ** Message: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: Le processus indicator-application main (8037) a été tué par le signal TERM upstart: Le processus indicator-application main s'est achevé, redémarrage ** (lightdm-gtk-greeter:7987): WARNING **: [PIDs] Failed to terminate process #7989: Aucun processus de ce type ** Message: Starting lightdm-gtk-greeter 2.0.1 (Apr 11 2016, 06:05:31) ** Message: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_ubuntu.conf ** Message: [Configuration] Reading file: /usr/share/lightdm/lightdm-gtk-greeter.conf.d/30_xubuntu.conf ** Message: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf upstart: Le processus indicator-application main (8126) s'est achevé avec l'état 1 upstart: Le processus indicator-application main s'est achevé, redémarrage upstart: Le processus indicator-messages main s'est achevé, redémarrage ** (lightdm-gtk-greeter:8080): WARNING **: [PIDs] Failed to terminate process #8082: Aucun processus de ce type upstart: Le processus indicator-messages main (8152) a été tué par le signal TERM upstart: Le processus indicator-application main (8151) a été tué par le signal TERM Regards, -- Stephane Peters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/913323 Title: Occasional login failure and artefacts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/913323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771604] [NEW] Binary missing from bwbar package
Public bug reported: Ubuntu 18.04 LTS / bwbar (1.2.3-3) [universe] The official package is missing the binary ( /usr/sbin/bwbar ) # service bwbar status ... ...: Starting bandwidth bar daemon: start-stop-daemon: unable to stat /usr/sbin/bwbar (No such file or directory) ... # dpkg -L bwbar /. /etc /etc/default /etc/default/bwbar /etc/init.d /etc/init.d/bwbar /usr /usr/share /usr/share/doc /usr/share/doc/bwbar /usr/share/doc/bwbar/README /usr/share/doc/bwbar/README.Debian /usr/share/doc/bwbar/changelog.Debian.gz /usr/share/doc/bwbar/copyright /usr/share/man /usr/share/man/man8 /usr/share/man/man8/bwbar.8.gz Also checked on https://packages.ubuntu.com/bionic/amd64/bwbar/filelist (same for each architecture) ** Affects: bwbar (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/1771604 Title: Binary missing from bwbar package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bwbar/+bug/1771604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1724657] Re: Boot freeze with Ubuntu 17.10 Live ISO on Surface Book
It would be interesting to try the linux kernel v4.15, it had solved a boot freeze on my side. See : https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1724657 Title: Boot freeze with Ubuntu 17.10 Live ISO on Surface Book To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1724657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Boot freeze due to intel-microcode
** Changed in: intel-microcode (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Boot freeze due to intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M
Tested again with a fresh install of Ubuntu 18.04. Linux kernel version 4.15.0-20 The boot freeze is still here, it happens just after giving my password, exactly when clicking on "login" (Gnome Desktop environment). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Boot freeze due to intel-microcode
Today, I retried "intel-microcode" on Xubuntu 18.04 fresh install and I was able to reboot 6 times in a row without any freeze. ~$ dmesg | grep microcode [0.00] microcode: microcode updated early to revision 0xc2, date = 2017-11-16 [0.987572] microcode: sig=0x506e3, pf=0x20, revision=0xc2 [0.987975] microcode: Microcode Update Driver: v2.2. Linux kernel version 4.15.0-20 So, it looks that the bug has been repaired by that linux v4.15 branch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Boot freeze due to intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M
That procedure also broke 2 things into my Xubuntu 17.10 : - Ethernet connexion not working any-more - The Linux kernel version "n-1" is now tagged into the "auto-removable" category, that would leave me with only one kernel version installed (I have uninstalled the 4.17 RC1 version). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M
First, I uninstalled Virtualbox. Proprietary Nvidia drivers were never installed on my computer, there is the "nouveau.modeset=0" parameter into Grub. Then, I have installed : linux-image-4.17.0-041700rc1-generic_4.17.0-041700rc1.201804152230_amd64.deb and linux-headers-4.17.0-041700rc1-generic_4.17.0-041700rc1.201804152230_amd64.deb There was errors related to Nvidia during that installation (see log file attached). Then a 1st reboot worked. Then a 2nd reboot with the temporary manual removal of "nouveau.modeset=0" parameter into Grub (key "E" + "F10") provoked a unsuccessful boot with a command line prompt : Ubuntu 17.10 PC tty1 PC login: _ So I assume that the answer is : tag 'kernel-bug-exists-upstream' ** Attachment added: "Log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+attachment/5119045/+files/Log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117766/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117767/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117768/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117761/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117760/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117762/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M
apport information ** Tags added: apport-collected artful ** Description changed: When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX 950M" and a "Intel HD Graphics 530" graphic card, the boot process freezes. The cause is that the current Linux kernel does not include FOSS drivers for "Nvidia Geforce GTX 950M". The solution to avoid that freeze is to add the "nomodeset" grub boot parameter or to install the proprietary Nvidia driver. My concern is that you have to be aware of that circumvent when installing Ubuntu OS for the first time. I think that it would be more logical that the Linux kernel uses the low performance graphic card "Intel HD Graphics 530" by default, without trying to use "Nvidia Geforce GTX 950M" which is not natively supported. That would avoid the bad experience of boot freeze at first meeting. Computer : Model = Asus N752VX-GC164T Ubuntu 17.10 + --- + ApportVersion: 2.20.7-0ubuntu3.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC0D0p: user 1861 F...m pulseaudio + /dev/snd/controlC0: user 1861 F pulseaudio + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2018-01-13 (92 days ago) + InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) + Lsusb: + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 002: ID 0461:4d22 Primax Electronics, Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: ASUSTeK COMPUTER INC. N752VX + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-38-generic.efi.signed root=UUID=5b9acdb6-aa5b-4801-8cd6-40621a2028d4 ro nouveau.modeset=0 + ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 + PulseList: + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-4.13.0-38-generic N/A + linux-backports-modules-4.13.0-38-generic N/A + linux-firmware 1.169.3 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: yes + Hard blocked: no + Tags: artful + Uname: Linux 4.13.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 08/18/2016 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: N752VX.301 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: N752VX + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: ATN12345678901234567 + dmi.chassis.type: 10 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: + dmi.product.family: N + dmi.product.name: N752VX + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117757/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117765/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117764/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117763/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117758/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1764286/+attachment/5117759/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764286] [NEW] Boot freeze due to Nvidia Geforce GTX 950M
Public bug reported: When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX 950M" and a "Intel HD Graphics 530" graphic card, the boot process freezes. The cause is that the current Linux kernel does not include FOSS drivers for "Nvidia Geforce GTX 950M". The solution to avoid that freeze is to add the "nomodeset" grub boot parameter or to install the proprietary Nvidia driver. My concern is that you have to be aware of that circumvent when installing Ubuntu OS for the first time. I think that it would be more logical that the Linux kernel uses the low performance graphic card "Intel HD Graphics 530" by default, without trying to use "Nvidia Geforce GTX 950M" which is not natively supported. That would avoid the bad experience of boot freeze at first meeting. Computer : Model = Asus N752VX-GC164T Ubuntu 17.10 ** Affects: linux (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/1764286 Title: Boot freeze due to Nvidia Geforce GTX 950M To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Boot freeze due to intel-microcode
In my case, the freeze occurs very early in the boot process. In the case of #1759920, the freeze occurs at login. Maybe the 2 bugs are related, but the behaviour is not the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Boot freeze due to intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Boot freeze due to intel-microcode
** Summary changed: - Regression in 2017-07-07 updates + Boot freeze due to intel-microcode -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Boot freeze due to intel-microcode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
Today, I installed manually : sudo dpkg -i intel-microcode_3.20180312.0~ubuntu18.04.1_amd64.deb No change, the freeze -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
Today, I installed manually : sudo dpkg -i intel-microcode_3.20180312.0~ubuntu18.04.1_amd64.deb No change, the freeze still occurs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
With or without intel-microcode installed : "journalctl -b | grep ply" gives no result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
Some news : Last week I saw a "grub" package update so I reinstalled the "intel- microcode" package, the freezing bug is still there on my configuration but there is one difference. With the "intel-microcode" package, at boot there is always a message that appears during approximately 1 second : error: invalid video mode specification `text'. Booting in blind mode It could be related to the fact that I am booting with the "nouveau.modeset=0" option. But without the "intel-microcode" package, I can't see (or don't have the time to) see that message. Sorry if this message is not related to the bug. I post it in case of. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
Some news : - Install of Debian 9.3 Stable 31 Jan 2018 (Linux kernel 4.9) : Boot always works - Install of Debian Testing 31 Jan 2018 (Linux kernel 4.14) : Random freeze at boot So considering my investigations until here, I consider that "intel- microcode v3.20180108.0+really20170707ubuntu17.10.1" doesn't work on my hardware/software config with a too recent Linux kernel, but I haven't any clue or detail on what is happening. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
- There is nothing about Refind into "journalctl -b". - I am not mixing DEs, I use only Xfce. - What does "S3 recovery" mean ? Samsung Galaxy S3 recovery ? - The bug occurs since the first boot of that Xubuntu install (at that time it was the 20180108 Intel CPU microcode), so I won't try to clean the system. Moreover the freeze occurs before that I have the opportunity to enter the LUKS passphrase, at that time only the /boot partition is accessible. So, in my opinion, the only candidates for the bug are : Hardware - UEFI Bios - EFI partition - Refind - Grub - Something inside the /boot folder. Thank you for your help and for all that time you spent to help me. But I have to admit that I currently need to take some rest away from that bug. I will uninstall "intel-microcode" for the moment, as anyway the current version doesn't provide any defence against Spectre/Meltdown. I will see what the next intel update gives. Also ASUS is supposed to provide "soon" a Bios update for my computer. Have a good day, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
Some tests I just did : - "journalctl | grep refind > refind.txt" > Empty file - Currently, I am booting like that : UEFI > Refind > Grub > Linux kernel - Chainloading the UEFI directly to Grub (no use of Refind) : gives the same random bug - Chainloading the Refind directly to Linux kernel (no use of Grub) : gives the same random bug and when it passes, it bugs later at a busybox prompt because I guess that Refind is not able to boot alone an OS installed on a LUKS partition. - Install of Debian 9.3 Stable : Boot always works (Linux 4.9 kernel) - UEFI > Refind > Grub (advanced menu) > Ubuntu with Linux 4.13.0-32 > Gives the same random bug but then I have a display of 2 lines before the freeze. Those 2 lines are : Loading Linux 4.13.0-32-generic ... Loading initial ramdisk ... I am wondering if I could circumvent the bug with the use of an old linux kernel on Xubuntu. Is is possible to install the 4.9 linux version on Xubuntu 17.10 without breaking the OS ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
If I boot a “vanilla” Ubuntu live USB, Does the "last CPU firmware" will be applied at reboot or will it disappear ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1529276] Re: Local keyboard layout is selected only after entering full system encryption key
That Bug affects Xubuntu 17.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1529276 Title: Local keyboard layout is selected only after entering full system encryption key To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1529276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
Thanks for the help, I have checked the timestamps into the 3 logs : It always corresponds to the successful boot. "journalctl -b" gives text I can't interpret, anyway it always corresponds to the last boot (successful). The Bios version is the most up to date one : v301 (13 oct 2016) The "quiet splash" option doesn't give any output to the screen when removed. I already checked that in the past and I re-tested today. I forgot to mention that the freeze occurs just after the Grub automatic selection. I guess the crash occurs in between Grub and kernel init. The bios UI is really limited, and I don't remember going there since a long time (except for boot priority). Moreover that bug doesn't occur when the package "intel-microcode" is removed. Additional hints : - There is a big chance that I installed Xubuntu from a USB key created with UnetBootin (I saw it gives problem with Debian) - I am using the rEFInd Boot Manager on top of Grub -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
See attached, the output of : journalctl -b | grep ERROR > ERROR.txt ** Attachment added: "ERROR.txt" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045552/+files/ERROR.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
See attached, the output of : journalctl -b | grep intel > intel.txt ** Attachment added: "intel.txt" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045553/+files/intel.txt ** Description changed: The version "3.20180108.0+really20170707ubuntu17.10.1" of the package "intel-microcode" randomly freezes Ubuntu at boot (at a very early stage, nothing is written on the screen). The number of hard reset of the computer required looks random but it works at third boot most of the time. I was previously affected by the 20180808 regression : https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742933 Symptoms are the same. user@PC:~$ dmesg | grep microcode [0.00] microcode: microcode updated early to revision 0xba, date = 2017-04-09 [0.986254] microcode: sig=0x506e3, pf=0x20, revision=0xba [0.986730] microcode: Microcode Update Driver: v2.2. If I uninstall "intel-microcode" everything is fine. user@PC:~$ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 This install is relatively fresh as I did it when I was affected by the 20180808 regression. Xubuntu 17.10 installed on a SSD with LUKS encryption user@PC:~$ uname -a Linux PC 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Package Manager = synaptic 0.84.2 Computer : Model = Asus N752VX-GC164T Bios = v301 (13 oct 2016) - Processor = Intel Core i7-6700HQ (6e gen Skylake) + Processor = Intel Core i7-6700HQ (6th gen Skylake) Nvidia graphic card = Grub is configured with "nouveau.modeset=0" Sorry I can't give more accurate description of the bug. I don't see any error message on the screen at boot. Is there somewhere a boot log I can provide ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] Re: Regression in 2017-07-07 updates
See attached, the output of : journalctl -b | grep error > error.txt ** Attachment added: "error.txt" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+attachment/5045551/+files/error.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1746200] [NEW] Regression in 2017-07-07 updates
Public bug reported: The version "3.20180108.0+really20170707ubuntu17.10.1" of the package "intel-microcode" randomly freezes Ubuntu at boot (at a very early stage, nothing is written on the screen). The number of hard reset of the computer required looks random but it works at third boot most of the time. I was previously affected by the 20180808 regression : https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742933 Symptoms are the same. user@PC:~$ dmesg | grep microcode [0.00] microcode: microcode updated early to revision 0xba, date = 2017-04-09 [0.986254] microcode: sig=0x506e3, pf=0x20, revision=0xba [0.986730] microcode: Microcode Update Driver: v2.2. If I uninstall "intel-microcode" everything is fine. user@PC:~$ lsb_release -rd Description:Ubuntu 17.10 Release:17.10 This install is relatively fresh as I did it when I was affected by the 20180808 regression. Xubuntu 17.10 installed on a SSD with LUKS encryption user@PC:~$ uname -a Linux PC 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Package Manager = synaptic 0.84.2 Computer : Model = Asus N752VX-GC164T Bios = v301 (13 oct 2016) Processor = Intel Core i7-6700HQ (6e gen Skylake) Nvidia graphic card = Grub is configured with "nouveau.modeset=0" Sorry I can't give more accurate description of the bug. I don't see any error message on the screen at boot. Is there somewhere a boot log I can provide ? ** Affects: intel-microcode (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/1746200 Title: Regression in 2017-07-07 updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1746200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1717293] [NEW] Grub crash
Public bug reported: Sorry, in french, I have: "l'éxécution de "grub-install /dev/sdb" a échoué. Cette erreur fatale" I don't know what else to do... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.3 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CasperVersion: 1.376.2 Date: Thu Sep 14 17:30:12 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.3 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1717293 Title: Grub crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1717293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys
Used the workaround in #12, but it is still a major annoyance that gnome-keyring-daemon does not handle this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/771272 Title: gnome-keyring doesn't support ecdsa or ed25519 keys To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/771272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695870] Re: [regression] sssd won't start if autofs is not installed
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1695870 Title: [regression] sssd won't start if autofs is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1695870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1695870] [NEW] [regression] sssd won't start if autofs is not installed
Public bug reported: The fix for LP# 1566508 (in Ubuntu 14.04 at least) introduces a regression that prevents sssd from starting if the autofs package is not installed. The /etc/init/sssd.conf script now has: ``` start on (filesystem and net-device-up and starting autofs) ``` The "starting autofs" will never happen if autofs is not installed. That's critical in that that prevents authentication after the next boot after "sssd" has been upgraded. The work around for now is to remove that "and starting autofs" or install the autofs package. ``` $ apt-cache policy sssd sssd: Installed: 1.11.8-0ubuntu0.6 Candidate: 1.11.8-0ubuntu0.6 Version table: *** 1.11.8-0ubuntu0.6 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.11.5-1ubuntu3 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ``` ** Affects: sssd (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/1695870 Title: [regression] sssd won't start if autofs is not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1695870/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1566508] Re: autofs races with sssd on startup
The fix in 14.04 causes sssd to not start on boot when "autofs" is not installed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1566508 Title: autofs races with sssd on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1566508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1693320] [NEW] subprocess installed post-installation script returned error exit status 1
Public bug reported: after updating from ubuntu 14.04 to 16.04, my pc hang and I need to shutdown manually. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libvirt-bin 1.3.1-1ubuntu10.10 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed May 24 13:31:12 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-09-16 (616 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=e3760653-6ef6-4f25-8dc3-5edd3b3dc540 ro quiet splash vt.handoff=7 SourcePackage: libvirt Title: package libvirt-bin 1.3.1-1ubuntu10.10 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-05-19 (4 days ago) modified.conffile..etc.libvirt.qemu.networks.default.xml: [modified] mtime.conffile..etc.libvirt.qemu.networks.default.xml: 2017-05-19T15:47:09.680314 ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1693320 Title: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1693320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1658921] Re: NetworkManager does not manage wired connection
Got hit by that one and lost several hours until I found the described workaround in the duplicate issue. This is really very bad. It prevents ethernet users from using network-manager-defined VPNs too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1658921 Title: NetworkManager does not manage wired connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1647275] [NEW] package account-plugin-owncloud (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi a
Public bug reported: account-plugin-owncloud failed to install ProblemType: Package DistroRelease: Ubuntu 16.10 Package: account-plugin-owncloud (not installed) ProcVersionSignature: Ubuntu 4.8.0-28.30-generic 4.8.6 Uname: Linux 4.8.0-28-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 AptOrdering: account-plugin-owncloud:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Dec 5 07:48:13 2016 ErrorMessage: tentative de remplacement de « /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au paquet owncloud-client 2.2.2+dfsg-1 InstallationDate: Installed on 2016-12-04 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: account-plugins Title: package account-plugin-owncloud (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au paquet owncloud-client 2.2.2+dfsg-1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: account-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1647275 Title: package account-plugin-owncloud (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/icons/hicolor/32x32/apps/owncloud.png », qui appartient aussi au paquet owncloud-client 2.2.2+dfsg-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1647275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637855] [NEW] Composite characters or Japanese input gets sometimes sent to the wrong terminal window
Public bug reported: At times (I have not found the trigger to reproduce it at will), one terminal window out of many will refuse to receive complex input sequences (such as the French composite accented character "ê" (which is typed with "^ + e" on a french keyboard), or IBus/Anthy Japanese input), and only these characters will be redirected to another terminal window. This means that for two terminals, typing in terminal 1 : "Verbe être" results in this : Terminal 1 : "Verbe tre" Terminal 2 : "ê" When this happens, the following workarounds work to put things in order : - close the affected terminal window - spawn a new one and close it I am not sure whether this is an IBus problem, or a Gnome Terminal problem at its core. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-terminal 3.16.2-1ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Mon Oct 31 01:51:06 2016 InstallationDate: Installed on 2010-01-30 (2465 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to wily on 2016-04-16 (197 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637855 Title: Composite characters or Japanese input gets sometimes sent to the wrong terminal window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1637855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637823] [NEW] keyboard input is not processed in the right order during high CPU load times
Public bug reported: I have noticed several issues with keyboard input processing, that can all seemingly be tied to high CPU usage. For context, I am using a french keyboard, and also need to type Japanese, which has me using IBus and Anthy. I think at some point in Ubuntu, the way input was handled changed drastically, and ever since I have been dealing with the following issues : - Composite keys such as ^ (^ + e => ê) used in French for accents are processed in a weird way : Suppose I type "Le verbe être est", I sometimes end up with "Le verbe treê est" actually appearing when typing under high CPU load. (Hinting at the fact that the ^ key stroke processing happens asynchronously, and without accounting for the proper and expected order of strokes, which is extremely annoying) (I mainly see this specific problem in applications such as Chrome, Skype for Linux Alpha, Discord, Slack.) Before I found a suggestion to set IBUS_ENABLE_SYNC_MODE=1 in my session environment, keyboard input order would end up completely shuffled. Enforcing sync mode nearly fixed everything except for composite keys. - When switching between French and Japanese, I have defined a specific shortcut to do the switching for me, and I am used to the switching taking time. The problem is that switching does not lock any input after that, so that it would be processed AFTER the switch was complete. When typing "tesuto" I expect the following to be input : てすと But I get the following : teすと This one, I am thinking is caused by asynchronous input processing for the shortcut keys, and the Anthy process taking time to get called back from swap memory. I would be perfectly fine with the previous behavior, and waiting three seconds, as long as input would be processed all at once, in the order I typed it. The above two problems mean I have to actually watch at what times I am going to need to use accented characters, or to type Japanese, and WAIT for the computer to finish switching before resuming typing. These literally halve my typing speed because I can't rely on muscle memory anymore when typing any language other than English. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Oct 30 20:45:04 2016 InstallationDate: Installed on 2010-01-30 (2464 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: ibus UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637823 Title: keyboard input is not processed in the right order during high CPU load times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1637823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637822] [NEW] autosave freezes editor and loses keystrokes
Public bug reported: The very useful autosave feature that runs every five minutes locks up the editor when it runs, and when it happens, any keystrokes typed during the interval are lost. Such that when typing the following (for example) : abcdefghijklmnopqrstuvwxyz If autosave runs during that interval, here is an example of what ends up being processed : abcdefghpqrstuvwxyz As is obvious, keystrokes for "ijklmno" are lost. This happens every time. I am not sure if this is specific to gedit, or to the input framework I am using (IBus, and at times Anthy for Japanese input) This is quite annoying as it forces me to re-read absolutely everything I typed to make sure gedit did not miss anything. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gedit 3.10.4-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Oct 30 20:37:04 2016 InstallationDate: Installed on 2010-01-30 (2464 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1) SourcePackage: gedit UpgradeStatus: Upgraded to wily on 2016-04-16 (196 days ago) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637822 Title: autosave freezes editor and loses keystrokes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1637822/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
I upgraded to older version 3.18.1-1ubuntu3, and relaunched metacity using "metacity --replace", and now I have metacity crashes, but they don't log me out. Just wondering if the fact I "replaced" metacity while logged in untied it from gnome-session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574125] Re: suspend not working after upgrade
Install the new kernel 4.4.8 from here http://linuxdaddy.com/blog/install-kernel-4-4-on-ubuntu/ Solve the problem. This is a bug into the 4.4.0 kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574125 Title: suspend not working after upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
