similar to: [Bug 109187] New: [NVC1][optimus] nouveau black display, only mouse cursor visible

https://bugs.freedesktop.org/show_bug.cgi?id=110748 Bug ID: 110748 Summary: [NVC1] [optimus] fifo: read fault at 0000000000 engine 00 [PGRAPH] client 00 [] reason 02 [PAGE_NOT_PRESENT] Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal

https://bugs.freedesktop.org/show_bug.cgi?id=105174 Bug ID: 105174 Summary: [regression] BUG unable to handle kernel NULL pointer dereference in kernel 4.15.3 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: All Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=105319 Bug ID: 105319 Summary: DRM: EVO timeout with kernel 4.15.x Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau Assignee: nouveau

it seems that when you say "check for new mail" in apple mail, it sends a NOOP to the imap server to get the response. in uw, the conversation is something like: 25 NOOP 25 OK NOOP completed 26 NOOP * 2796 EXISTS * 7 RECENT 26 OK NOOP completed however, with dovecot, if it has already notified the client that new mail has arrived, it will look something like: * 24 EXISTS * 2 RECENT

When connecting with mutt via IMAPS, I get "connection to server closed" and this appears in logs: dovecot: Feb 04 12:48:30 Error: IMAP(rathann): file mail-index-sync-ext.c: line 118: assertion failed: (size <= synch_size) The problem goes away after deleting the index from ~/Mail/.imap/INBOX. We're running 1.0-test62 on Solaris 9. -- Dominik 'Rathann' Mierzejewski

Hi, Got the following today with test62 and mbox: IMAP(juergen): Fixed index file /home/juergen/Mail/.imap/INBOX/dovecot.index: recent_messages_count 19 -> 0 imap-login: Login: juergen [192.168.0.1] file mail-index-sync-ext.c: line 118 (mail_index_sync_deinit_handlers): assertion failed: (size <= synch_size) child 31196 (imap) killed with signal 6 after that I had to delete

Has anybody managed to have Dovecot authenticate to Microsoft Active Directory? I've tried to get it to work using LDAP and the following settings dovecot.conf: userdb = ldap /etc/dovecot-ldap.conf passdb = ldap /etc/dovecot-ldap.conf dovecot-ldap.conf: hosts = rdg-home.ad.rdg.ac.uk dn = cn=bind-user,cn=users,dc=rdg-home,dc=ad,dc=rdg,dc=ac,dc=uk dnpass = XXXXX ldap_version = 2 base =

I've been experimenting with dovecot-1.0-stable on Solaris. Storage format is mbox. Dovecot, in test, runs in parallel with an UW IMAP, with dovecot running SSL-only on port 994. It seems to work to some extent: * dovecot runs * authentication works * SSL works * all manual IMAP functionality checks seem to work fine However, I'm running into issues with IMAP clients. * Null

Hi When building with GCC 10, gcc is stricter in handling handling of symbol clashes. Fedora, has fixed this with a patch from Dominik Mierzejewski: https://src.fedoraproject.org/rpms/tftp/c/5e2aa55b6802a52ef480d688b3ae4751220f20e0.patch Attaching the corresponding patch for git am. Regards, Salvatore >From 9e7641bf58df9dda3bc51f381f371fa7cbce47af Mon Sep 17 00:00:00 2001 From: Salvatore

Hi When building with GCC 10, gcc is stricter in handling handling of symbol clashes. Fedora, has fixed this with a patch from Dominik Mierzejewski: https://src.fedoraproject.org/rpms/tftp/c/5e2aa55b6802a52ef480d688b3ae4751220f20e0.patch Attaching the corresponding patch for git am. I'm sending the patch which was submitted a while ago to the list. Is there something you wanted to be

https://bugs.freedesktop.org/show_bug.cgi?id=99900 poma <pomidorabelisima at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nouveau: freeze / crash |[NVC1] nouveau: freeze / |after kernel update to 4.10 |crash after kernel update

https://bugs.freedesktop.org/show_bug.cgi?id=99900 --- Comment #12 from Antoine Saroufim <antoine.saroufim at gmail.com> --- I'm experiencing the same issues. Nouveau (Gallium 0.4 - NVC1) freezes everything on Wayland, sometimes the kernel too and it turns the display into a black screen with a visible cursor on X11. I've noticed this since I've upgraded to kernel 4.10. Here are

https://bugs.freedesktop.org/show_bug.cgi?id=111525 Bug ID: 111525 Summary: [NVC1] Kernel crashes when launching Steam remote play Product: Mesa Version: 19.1 Hardware: Other OS: All Status: NEW Severity: normal Priority: not set Component: Drivers/DRI/nouveau Assignee:

https://bugs.freedesktop.org/show_bug.cgi?id=84721 r004 <roo4.id at gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|roo4.id at gmail.com |nouveau at lists.freedesktop.o | |rg -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=84721 --- Comment #10 from Krzysztof Katowicz-Kowalewski <vnd at vndh.net> --- As far as I've checked, the problem appeared in 3.15 kernel. I've tried hardened-sources-3.14.29 and there's no problem with the fan, at least in auto mode. But since you change the mode to manual (echo 1 > pwm1_enable), the fan gets mad as in 3.15

https://bugs.freedesktop.org/show_bug.cgi?id=84721 --- Comment #11 from r004 <roo4.id at gmail.com> --- (In reply to Krzysztof Katowicz-Kowalewski from comment #10) > As far as I've checked, the problem appeared in 3.15 kernel. I've tried > hardened-sources-3.14.29 and there's no problem with the fan, at least in > auto mode. But since you change the mode to manual

https://bugs.freedesktop.org/show_bug.cgi?id=84721 --- Comment #12 from Krzysztof Katowicz-Kowalewski <vnd at vndh.net> --- @r004, I had the same problem with my system and I've made little investigation. Indeed the problem appeared in 3.15 and it's still there in latest 3.18 kernel. For the quick and easy work-around use kernel 3.14 or lower. -- You are receiving this mail

https://bugs.freedesktop.org/show_bug.cgi?id=84721 --- Comment #13 from Ilia Mirkin <imirkin at alum.mit.edu> --- (In reply to Krzysztof Katowicz-Kowalewski from comment #12) > @r004, I had the same problem with my system and I've made little > investigation. Indeed the problem appeared in 3.15 and it's still there in > latest 3.18 kernel. For the quick and easy work-around

https://bugs.freedesktop.org/show_bug.cgi?id=84721 Tobias Klausmann <tobias.klausmann at mni.thm.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal -- You are receiving this mail because: You are the assignee for the bug. --------------

https://bugs.freedesktop.org/show_bug.cgi?id=84721 --- Comment #14 from Krzysztof Katowicz-Kowalewski <vnd at vndh.net> --- After 7 tries... here's the culprit: localhost linux # git bisect good 0e994d645627bb67088ae4860e9a0295b123f7b0 is the first bad commit commit 0e994d645627bb67088ae4860e9a0295b123f7b0 Author: Martin Peres <martin.peres at labri.fr> Date: Wed Feb 19