Re: CFT for vendor openzfs - week 4 reminder + memdisk images
On Tue, 28 Jul 2020 21:16:28 -0700 Matthew Macy mm...@freebsd.org said On Tue, Jul 28, 2020 at 21:06 Chris wrote: > On Tue, 28 Jul 2020 20:50:33 -0700 Matthew Macy mm...@freebsd.org said > > > On Tue, Jul 28, 2020 at 20:43 Chris wrote: > > > > > On Tue, 28 Jul 2020 20:08:33 -0700 Matthew Macy mm...@freebsd.org said > > > > > > > On Tue, Jul 28, 2020 at 8:03 PM Chris > wrote: > > > > > > > > > > On Tue, 28 Jul 2020 19:10:21 -0700 Matthew Macy mm...@freebsd.org > said > > > > > > > > > > > On Wednesday, July 8th I issued the initial call for testing for > the > > > > > > update to HEAD to vendored openzfs. We'd like to give users > roughly a > > > > > > month to test before merging. The tentative merge date is August > > > > > > 17th. > > > > > > > > > > > > Again, I hope it's not terribly controversial to point out that > > > > > > it really rests with users of non amd64 platforms to test to > avoid > > > any > > > > > > unpleasant surprises the next time they update their trees > following > > > > > > the merge. > > > > > > > > > > > > amd64, i386, and aarch64 memdisk images can be found at: > > > > > > > > > > > > > > > > > > > https://people.freebsd.org/~freqlabs/freebsd-openzfs-3d833bea-f10f94aa-2020072900/ > > > > > > > > > > Is this in an attempt to replace the opensolaris version used now? > > > > > > > > The word "attempt" is a misnomer. If you search the mail archives > this > > > > has been the PoR for some time. > > > Sure. OK. I caught this thread. But must have missed the announcement > > > of the intent to replace the opensolaris version with openzfs. > > > Do you recall which mailing list that was made to? > > > > > > Thank you for your quick reply, Matthew. > > > > > > > Apart from the 3 previous CFT mails, the initial intent was discussed in > > December 2018. Getting FreeBSD support integrated in to openzfs took a > lot > > more incremental PRs than I anticipated. > > > > > > https://lists.freebsd.org/pipermail/freebsd-current/2018-December/072422.html > > Thank you very much, Mathew. Sorry for any bother. > No bother or not much at least. It’s just been a long haul and I’d like to wrap this up. No doubt. FTR I'm not looking to impede you. :-) My only concern would be that I'd need to remaster the art of ZFS. I've got 1500 installs to maintain, and any changes tend to alarm me. :-) I see we're a bit behind the others, if this status report is current: https://docs.google.com/spreadsheets/d/1CFapSYxA5QRFYy5k6ge3FutU7zbAWbaeGN2nKVXgxCI/edit#gid=0 Will your impending commit move us closer? Is there anything others like myself can do to help? Thanks again, Matthew. --Chris -M > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Poul-Henning Kamp wrote: > When I start cad/kicad (which I have not done in some time), the > gui is horribly lagging and often downright confused about > the cursors whereabouts. May not be relevant but FWIW I saw similar issue with kdenlive-19.12 on 11.3 kdenlive-18.x worked fine [kdenlive] [Bug 417031] ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Michael Gmelin writes: > > > > On 29. Jul 2020, at 21:29, Poul-Henning Kamp wrote: > > > > Michael Gmelin writes: > > > >> I meant which xorg driver - modesetting or Intel? > > > > It looks like "modesetting": > > > > You could try installing xf86-video-intel and see if that makes a difference > (in terms of artifacts, can't imagine it has anything to do with the focus > issue?!). That seems to have taken care of the scroll-bar flickering, will see how it goes. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
> On 29. Jul 2020, at 21:29, Poul-Henning Kamp wrote: > > > Michael Gmelin writes: > >> I meant which xorg driver - modesetting or Intel? > > It looks like "modesetting": > You could try installing xf86-video-intel and see if that makes a difference (in terms of artifacts, can’t imagine it has anything to do with the focus issue?!). Unfortunately, I use the machine I have around that’s similar to yours for something productive at the moment, so I can’t update it to current to try myself. -m >[ 149.032] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so >[ 149.038] (II) Module glx: vendor="X.Org Foundation" >[ 149.038]compiled for 1.20.8, module version = 1.0.0 >[ 149.038]ABI class: X.Org Server Extension, version 10.0 >[ 149.038] (==) Matched intel as autoconfigured driver 0 >[ 149.038] (==) Matched modesetting as autoconfigured driver 1 >[ 149.038] (==) Matched scfb as autoconfigured driver 2 >[ 149.038] (==) Matched vesa as autoconfigured driver 3 >[ 149.038] (==) Assigned the driver to the xf86ConfigLayout >[ 149.038] (II) LoadModule: "intel" >[ 149.038] (WW) Warning, couldn't open module intel >[ 149.038] (EE) Failed to load module "intel" (module does not exist, 0) >[ 149.038] (II) LoadModule: "modesetting" >[ 149.038] (II) Loading > /usr/local/lib/xorg/modules/drivers/modesetting_drv.so >[ 149.039] (II) Module modesetting: vendor="X.Org Foundation" >[ 149.039]compiled for 1.20.8, module version = 1.20.8 >[ 149.039]Module class: X.Org Video Driver >[ 149.039]ABI class: X.Org Video Driver, version 24.1 > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Michael Gmelin writes: > I meant which xorg driver - modesetting or Intel? It looks like "modesetting": [ 149.032] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [ 149.038] (II) Module glx: vendor="X.Org Foundation" [ 149.038]compiled for 1.20.8, module version = 1.0.0 [ 149.038]ABI class: X.Org Server Extension, version 10.0 [ 149.038] (==) Matched intel as autoconfigured driver 0 [ 149.038] (==) Matched modesetting as autoconfigured driver 1 [ 149.038] (==) Matched scfb as autoconfigured driver 2 [ 149.038] (==) Matched vesa as autoconfigured driver 3 [ 149.038] (==) Assigned the driver to the xf86ConfigLayout [ 149.038] (II) LoadModule: "intel" [ 149.038] (WW) Warning, couldn't open module intel [ 149.038] (EE) Failed to load module "intel" (module does not exist, 0) [ 149.038] (II) LoadModule: "modesetting" [ 149.038] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so [ 149.039] (II) Module modesetting: vendor="X.Org Foundation" [ 149.039]compiled for 1.20.8, module version = 1.20.8 [ 149.039]Module class: X.Org Video Driver [ 149.039]ABI class: X.Org Video Driver, version 24.1 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
On Wed, 29 Jul 2020 at 15:18, Poul-Henning Kamp wrote: > > > Michael Gmelin writes: > > > Which driver are you using? > > drm-devel-kmod-5.3.g20200724 I'm using drm-kmod built from https://github.com/freebsd/drm-kmod at 6aeae91adbebae15bb77ccdc87f4e0a1d9fcb184 ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
> On 29. Jul 2020, at 21:18, Poul-Henning Kamp wrote: > > > Michael Gmelin writes: > >> Which driver are you using? > > drm-devel-kmod-5.3.g20200724 > I meant which xorg driver - modesetting or Intel? -m > dmesg: > >drmn0: on vgapci0 >vgapci0: child drmn0 requested pci_enable_io >vgapci0: child drmn0 requested pci_enable_io >[drm] Unable to create a private tmpfs mount, hugepage support will be > disabled(-19). >__pm_runtime_resume not implemented -- see your local kernel hacker >pm_runtime_mark_last_busy not implemented -- see your local kernel hacker >__pm_runtime_suspend not implemented -- see your local kernel hacker >Failed to add WC MTRR for [0x8000-0x9fff]: -22; performance may > suffer >[drm] Got stolen memory base 0x7d80, size 0x200 >[drm] Supports vblank timestamp caching Rev 2 (21.10.2013). >[drm] Driver supports precise vblank timestamp query. >[drm] Connector eDP-1: get mode from tunables: >[drm] - kern.vt.fb.modes.eDP-1 >[drm] - kern.vt.fb.default_mode >[drm] Connector DP-1: get mode from tunables: >[drm] - kern.vt.fb.modes.DP-1 >[drm] - kern.vt.fb.default_mode >[drm] Connector HDMI-A-1: get mode from tunables: >[drm] - kern.vt.fb.modes.HDMI-A-1 >[drm] - kern.vt.fb.default_mode >[drm] Connector DP-2: get mode from tunables: >[drm] - kern.vt.fb.modes.DP-2 >[drm] - kern.vt.fb.default_mode >[drm] Connector HDMI-A-2: get mode from tunables: >[drm] - kern.vt.fb.modes.HDMI-A-2 >[drm] - kern.vt.fb.default_mode >pm_runtime_get_if_in_use not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >register_oom_notifier not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >kmem_cache_shrink not implemented -- see your local kernel hacker >sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)! >[drm] Initialized i915 1.6.0 20190619 for drmn0 on minor 0 >register_acpi_notifier not implemented -- see your local kernel hacker >async_schedule is dodgy -- see your local kernel hacker >pm_runtime_set_autosuspend_delay not implemented -- see your local kernel > hacker >__pm_runtime_use_autosuspend not implemented -- see your local kernel > hacker >async_synchronize_cookie not implemented -- see your local kernel hacker >acpi_video0: on vgapci0 >WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD > 13.0. >VT: Replacing driver "vga" with new "fb". >[drm] Reducing the compressed framebuffer size. This may lead to less > power savings than a non-reduced-size. Try to increase stolen memory size if > available in BIOS. >start FB_INFO: >type=11 height=1080 width=1920 depth=32 >cmsize=16 size=14745600 >pbase=0x8004 vbase=0xf8008004 >name=drmn0 flags=0x0 stride=10240 bpp=32 >cmap[0]=0 cmap[1]=7f cmap[2]=7f00 cmap[3]=c4a000 >end FB_INFO >drmn0: fb0: i915drmfb frame buffer device >drmn0: successfully loaded firmware image with name: > i915/kbl_dmc_ver1_04.bin >[drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) > > > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Michael Gmelin writes: > Which driver are you using? drm-devel-kmod-5.3.g20200724 dmesg: drmn0: on vgapci0 vgapci0: child drmn0 requested pci_enable_io vgapci0: child drmn0 requested pci_enable_io [drm] Unable to create a private tmpfs mount, hugepage support will be disabled(-19). __pm_runtime_resume not implemented -- see your local kernel hacker pm_runtime_mark_last_busy not implemented -- see your local kernel hacker __pm_runtime_suspend not implemented -- see your local kernel hacker Failed to add WC MTRR for [0x8000-0x9fff]: -22; performance may suffer [drm] Got stolen memory base 0x7d80, size 0x200 [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [drm] Driver supports precise vblank timestamp query. [drm] Connector eDP-1: get mode from tunables: [drm] - kern.vt.fb.modes.eDP-1 [drm] - kern.vt.fb.default_mode [drm] Connector DP-1: get mode from tunables: [drm] - kern.vt.fb.modes.DP-1 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-1: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-1 [drm] - kern.vt.fb.default_mode [drm] Connector DP-2: get mode from tunables: [drm] - kern.vt.fb.modes.DP-2 [drm] - kern.vt.fb.default_mode [drm] Connector HDMI-A-2: get mode from tunables: [drm] - kern.vt.fb.modes.HDMI-A-2 [drm] - kern.vt.fb.default_mode pm_runtime_get_if_in_use not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker register_oom_notifier not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker kmem_cache_shrink not implemented -- see your local kernel hacker sysctl_warn_reuse: can't re-use a leaf (hw.dri.debug)! [drm] Initialized i915 1.6.0 20190619 for drmn0 on minor 0 register_acpi_notifier not implemented -- see your local kernel hacker async_schedule is dodgy -- see your local kernel hacker pm_runtime_set_autosuspend_delay not implemented -- see your local kernel hacker __pm_runtime_use_autosuspend not implemented -- see your local kernel hacker async_synchronize_cookie not implemented -- see your local kernel hacker acpi_video0: on vgapci0 WARNING: Device "fb" is Giant locked and may be deleted before FreeBSD 13.0. VT: Replacing driver "vga" with new "fb". [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. start FB_INFO: type=11 height=1080 width=1920 depth=32 cmsize=16 size=14745600 pbase=0x8004 vbase=0xf8008004 name=drmn0 flags=0x0 stride=10240 bpp=32 cmap[0]=0 cmap[1]=7f cmap[2]=7f00 cmap[3]=c4a000 end FB_INFO drmn0: fb0: i915drmfb frame buffer device drmn0: successfully loaded firmware image with name: i915/kbl_dmc_ver1_04.bin [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
> On 29. Jul 2020, at 21:02, Poul-Henning Kamp wrote: > > > Ed Maste writes: >>> On Wed, 29 Jul 2020 at 06:20, Poul-Henning Kamp wrote: >>> >>> I just noticed that KiCad's scroll-bars flash a lot whenever the mouse >>> pointer is moved, that sounds like it could be the focus-event-flooding. >> >> For me KiCad's scroll bars are hidden, and flash briefly on and off >> while the pointer's moving. This is with a USB mouse (trackball) >> attached, and xfwm4. > > I'm seing similar stuff, and sometimes I am also seeing some screen > artifacts which could implicate DRM :-( > Which driver are you using? > -- > Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > p...@freebsd.org | TCP/IP since RFC 956 > FreeBSD committer | BSD since 4.3-tahoe > Never attribute to malice what can adequately be explained by incompetence. > ___ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Ed Maste writes: > On Wed, 29 Jul 2020 at 06:20, Poul-Henning Kamp wrote: > > > > I just noticed that KiCad's scroll-bars flash a lot whenever the mouse > > pointer is moved, that sounds like it could be the focus-event-flooding. > > For me KiCad's scroll bars are hidden, and flash briefly on and off > while the pointer's moving. This is with a USB mouse (trackball) > attached, and xfwm4. I'm seing similar stuff, and sometimes I am also seeing some screen artifacts which could implicate DRM :-( -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Zitat von Christoph Moench-Tegeder : ## Poul-Henning Kamp (p...@phk.freebsd.dk): When I start cad/kicad (which I have not done in some time), the gui is horribly lagging and often downright confused about the cursors whereabouts. KiCad maintainer writing. I can't reproduce your problem on 12.1 (and I don't have a trackpad available). Can't reproduce with kicad-devel on RELENG_12 either. greetings --- Michael -- greetings --- mike m...@freebsd.org ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Christoph Moench-Tegeder writes: > KiCad maintainer writing. Many thanks maintaining KiCad, it's one of the tools I cannot live without. > > One of the few diagnostics I see related to this is: > > > > 07:33:34: Debug: window wxScrolledWindow(0x81a3f8000, ) lost focus even > though it didn't have it > > But this message exists even here. It's from wxWidgets (wx31-gtk3, > pulled in via wxPython) and the whole wx-thingy is slightly messy... > Anyways, I'd think this message itself is harmless. Ok, I will disregard that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
## Poul-Henning Kamp (p...@phk.freebsd.dk): > When I start cad/kicad (which I have not done in some time), the > gui is horribly lagging and often downright confused about > the cursors whereabouts. KiCad maintainer writing. I can't reproduce your problem on 12.1 (and I don't have a trackpad available). > One of the few diagnostics I see related to this is: > > 07:33:34: Debug: window wxScrolledWindow(0x81a3f8000, ) lost focus even > though it didn't have it But this message exists even here. It's from wxWidgets (wx31-gtk3, pulled in via wxPython) and the whole wx-thingy is slightly messy... Anyways, I'd think this message itself is harmless. Regards, Christoph -- Spare Space ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
On Wed, 29 Jul 2020 at 06:20, Poul-Henning Kamp wrote: > > I just noticed that KiCad's scroll-bars flash a lot whenever the mouse > pointer is moved, that sounds like it could be the focus-event-flooding. For me KiCad's scroll bars are hidden, and flash briefly on and off while the pointer's moving. This is with a USB mouse (trackball) attached, and xfwm4. Things seem normal other than the scroll bars though. I have a kernel and world from July 14, and packages a little older than that. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Poul-Henning Kamp writes: > > Michael Gmelin writes: > > > I might try to reproduce the issue myself later this week (if I happen > > to find some time and nobody else comes up with a solution). Which WM > > are you using? > > I just noticed that KiCad's scroll-bars flash a lot whenever the mouse > pointer is moved, that sounds like it could be the focus-event-flooding. I just checked: my x11-server is also -current as of sunday, so that D245854 patch is in place. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Michael Gmelin writes: > I might try to reproduce the issue myself later this week (if I happen > to find some time and nobody else comes up with a solution). Which WM > are you using? I just noticed that KiCad's scroll-bars flash a lot whenever the mouse pointer is moved, that sounds like it could be the focus-event-flooding. I'm using ctwm :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
On Wed, 29 Jul 2020 09:36:29 + "Poul-Henning Kamp" wrote: > > Michael Gmelin writes: > > > This sounds a bit like it could be related to > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245854 > > That sounds like something in the same zip code. > > > Two easy things you could check: > > - try connecting a usb mouse (to rule out synaptics being the > > issue). > > Dont have any at hand this week :-( > > > - try using a different WM and see if the problem persists. > > I dont see any reason to think this is WM related, it happens while > the cursor stays firmly inside kicad's windows. I had a similar issue with a window manager in the past (losing focus for some reason I didn't understand, it was when running chromium back then if I remember correctly) and I figured it's such a cheap check that it might be worth a shot. I might try to reproduce the issue myself later this week (if I happen to find some time and nobody else comes up with a solution). Which WM are you using? Cheers, Michael -- Michael Gmelin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Michael Gmelin writes: > This sounds a bit like it could be related to > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245854 That sounds like something in the same zip code. > Two easy things you could check: > - try connecting a usb mouse (to rule out synaptics being the issue). Dont have any at hand this week :-( > - try using a different WM and see if the problem persists. I dont see any reason to think this is WM related, it happens while the cursor stays firmly inside kicad's windows. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
Hans Petter Selasky writes: > Try to install "xev" and see if the log is full of events. I only see problems in kicad, everything else, including firefox and xev works fine (as far as I can tell) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
> On 29. Jul 2020, at 11:13, Poul-Henning Kamp > wrote: > > I updated to current three days ago: > >13.0-CURRENT #0 r363533M: Sun Jul 26 08:39:48 UTC 2020 > > When I start cad/kicad (which I have not done in some time), the > gui is horribly lagging and often downright confused about > the cursors whereabouts. > > I've tried switching between "fall-back" and "accellerated" > in kicad, but there does not seem to be any qualitative > difference. > > One of the few diagnostics I see related to this is: > >07:33:34: Debug: window wxScrolledWindow(0x81a3f8000, ) lost focus > even though it didn't have it > > I have no idea if this is a kicad, Xorg or libinput related. > This sounds a bit like it could be related to https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245854 Two easy things you could check: - try connecting a usb mouse (to rule out synaptics being the issue). - try using a different WM and see if the problem persists. Touch jumps are common and haven’t caused me any problems so far (then again, I'm not kicad user). -m -- Michael Gmelin ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: KiCad is horrible on CURRENT
On 2020-07-29 09:52, Poul-Henning Kamp wrote: I updated to current three days ago: 13.0-CURRENT #0 r363533M: Sun Jul 26 08:39:48 UTC 2020 When I start cad/kicad (which I have not done in some time), the gui is horribly lagging and often downright confused about the cursors whereabouts. I've tried switching between "fall-back" and "accellerated" in kicad, but there does not seem to be any qualitative difference. One of the few diagnostics I see related to this is: 07:33:34: Debug: window wxScrolledWindow(0x81a3f8000, ) lost focus even though it didn't have it I have no idea if this is a kicad, Xorg or libinput related. In my Xorg log I have a lot of (rate-limited): SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. Try to install "xev" and see if the log is full of events. --HPS ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
KiCad is horrible on CURRENT
I updated to current three days ago: 13.0-CURRENT #0 r363533M: Sun Jul 26 08:39:48 UTC 2020 When I start cad/kicad (which I have not done in some time), the gui is horribly lagging and often downright confused about the cursors whereabouts. I've tried switching between "fall-back" and "accellerated" in kicad, but there does not seem to be any qualitative difference. One of the few diagnostics I see related to this is: 07:33:34: Debug: window wxScrolledWindow(0x81a3f8000, ) lost focus even though it didn't have it I have no idea if this is a kicad, Xorg or libinput related. In my Xorg log I have a lot of (rate-limited): SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
