On Wed, Jun 1, 2016 at 10:57 PM, Daniel Jakots wrote:
> On Fri, 27 May 2016 16:18:48 +0200, David Coppa
> wrote:
>
>> On Fri, 27 May 2016, Carlin Bingham wrote:
>>
>> > On Fri, May 27, 2016 at 01:07:09AM +0200, Theo Buehler wrote:
>> > > On Thu, May
The first bug was already reported three years ago:
http://marc.info/?l=openbsd-bugs&m=135732012310459
std::ifstream has a bug when linked with libpthread:
$ cat t1.cpp
#include
#include
int
main(void)
{
std::ifstream fin("/");
std::cout << (!fin ? "BUG" : "OK") << std::endl;
On Tue, 24 May 2016, m...@extensibl.com wrote:
> >Synopsis: Default OpenBSD 5.9 GCC 4.2.1 compiler segfaults when
> >compiling a sample file
> >Category: system amd64
> >Environment:
> System : OpenBSD 5.9
> Details : OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:1
On Tue, May 24, 2016 at 4:42 PM, Stefan Kempf wrote:
> David Coppa wrote:
>> On Tue, 24 May 2016, m...@extensibl.com wrote:
>>
>> > >Synopsis: Default OpenBSD 5.9 GCC 4.2.1 compiler segfaults when
>> > >compiling a sample file
>> >
On Tue, 24 May 2016, Stefan Kempf wrote:
> Hmm, looking closer at your bugzilla link, this somewhat larger diff
> should also fix the same problem, but it was committed against GPLv2 sources.
> Still need to try it though.
>
> https://gcc.gnu.org/ml/gcc-patches/2006-11/msg00206.html
The larger d
On Wed, May 25, 2016 at 1:18 PM, David Coppa wrote:
> On Tue, 24 May 2016, Stefan Kempf wrote:
>
>> Hmm, looking closer at your bugzilla link, this somewhat larger diff
>> should also fix the same problem, but it was committed against GPLv2 sources.
>> Still need to tr
On Fri, 27 May 2016, Carlin Bingham wrote:
> On Fri, May 27, 2016 at 01:07:09AM +0200, Theo Buehler wrote:
> > On Thu, May 26, 2016 at 05:54:30PM -0400, Andre Smagin wrote:
> > > On Sat, 14 May 2016 21:01:29 +0200 (CEST)
> > > danj+o...@chown.me wrote:
> > >
> > > > >Synopsis: radeon(4) drm
Il 27/lug/2015 20:09, "Okan Demirmen" ha scritto:
>
> Hi - I gather this is the same if you quit fvwm, right? I suspect this
> is not window manager specific. Mind trying a more recent snapshot?
Indeed.
This is the infamous hang on exit with xserver, the vesa driver and Intel's
Broadwell gpu (it'
Il 22/set/2015 18:38, "Aaron Poffenberger" ha scritto:
>
> On 09/22/15 10:34, Philip Guenther wrote:
>>
>> On Tue, 22 Sep 2015, Ted Unangst wrote:
>>>
>>> Aaron Poffenberger wrote:
> Synopsis: System Hangs when Quitting X11 on Lenovo T450s
> Category: X11
> Environmen
On Fri, Dec 4, 2015 at 10:27 AM, wrote:
> My iPhone has some pretty big videos, over 10G. Sometimes using gphoto2 to
> list files crashes gphoto2, sometimes it causes a kernel panic. I'll try to
> get the dmesg later, but this is on amd64, November 30-ish snapshot.
>
> Here are the ddb trace an
On Thu, Aug 31, 2017 at 3:39 PM, Eda Sky wrote:
> Hi
>
> I use HP nc2400 i386 current from 15.7.2017? Before switching to clang.
>
> It worked fantastically zzz and ZZZ
> suspend several times a day to the last week
> After updating to current the system goes to sleep
> but it will freeze hard on
On Tue, Apr 22, 2014 at 10:29 AM, Kārlis Miķelsons
wrote:
>> It's the pms(4) driver. It happens on some Dell laptops that have a crappy
>> non fully standard synaptics (alps?) touchpad.
>
> It seems so, today this laptop booted up without pms device for some reason,
> and without it X.org started
On Thu, Apr 24, 2014 at 2:58 PM, Martin Pieuchot wrote:
> On 22/04/14(Tue) 20:30, Kārlis Miķelsons wrote:
>> >>>Try to disable pms:
>> >>>
>> >>># config -e -f /bsd
>> >>>UKC>disable pms
>> >>>
>> >>>And see if you can reproduce the problem.
>> >>I can, after disabling pms device, X.org starts jus
On Fri, Apr 25, 2014 at 7:24 AM, Kārlis Miķelsons
wrote:
>>> >Great. Could you compile a kernel with the diff below applied and post
>>> >its dmesg after starting Xorg. I'm guessing that the delay comes from
>>> >the fact that we are re-probing for the touchpad protocol, but having
>>> >this debu
On Tue, Sep 16, 2014 at 9:55 AM, wrote:
> someone fix current pls. month passed
Congratulations, You won the prize for most useless bug report ever done.
On Mon, Sep 29, 2014 at 10:50 AM, wrote:
>
> #0 0x in ?? ()
> #1 0x086c5482561e in tor_free_ () from /usr/local/bin/tor
> #2 0x086c548257d0 in tor_free_ () from /usr/local/bin/tor
> #3 0x086eeb0f48cb in ssl3_get_client_hello (s=0x86f47efe000) at
> /usr/src/lib/lib
On Mon, Sep 29, 2014 at 4:19 PM, wrote:
This bug has already been fixed.
Please update your tor port to the latest version (0.2.4.24)
> Program received signal SIGSEGV, Segmentation fault.
> 0x in ?? ()
> (gdb) bt
> #0 0x in ?? ()
> #1 0x18fdd39805a7 in pr
On Mon, Sep 29, 2014 at 7:03 PM, wrote:
> wonderful. it changes everything..
> ..or not?
Strange, since it does not crash on my machine with tor-0.2.4.24
Have you customized your /etc/tor/torrc?
How are you using tor? with polipo proxy or dante (socksify) ?
--
"If you try a few times and gi
On Mon, Sep 29, 2014 at 8:39 PM, wrote:
> torrc:
>
> Nickname PESEC
> User _tor
> RunAsDaemon 0
> DataDirectory /etc/tor
I think this is wrong, because /etc/tor is owned by root (unless
you've changed it). DataDirectory should be /var/tor.
> Log notice stderr
> ControlPort 9052
> HashedControlP
On Mon, Sep 29, 2014 at 10:59 PM, Stuart Henderson wrote:
> As a test (not a permanent solution), try
>
> ln -s j /etc/malloc.conf
>
> If this unbreaks things, there is most likely a use-after-free,
> especially because the timing seems to match the time when the
> malloc defaults were toughened i
On Tue, Sep 30, 2014 at 9:30 AM, wrote:
> it sounds funny, but you are doing something wrong :) i simply have no
> place to make a mistake.
> on virtual machine(i use vmware) install _CURRENT_, install mc, install
> tor(.24 from ports), run tor- this is exactly what i did. crashed
> immediately a
On Fri, Oct 3, 2014 at 9:36 PM, wrote:
> Oct 03 23:37:09.000 [notice] Now checking whether ORPort 5.165.74.63:9002 and
> DirPort 5.165.74.63:9031 are reachable... (this may take up to 20 minutes --
> look for log messages indicating success)
> Oct 03 23:37:11.000 [notice] Self-testing indicates
On Sun, Oct 5, 2014 at 8:28 PM, 1 wrote:
> hmm.. fixed? look like working ) you are the best, many many thanks ^^
I did nothing. jsing@ did this patch.
Ciao!
David
--
"If you try a few times and give up, you'll never get there. But if
you keep at it... There's a lot of problems in the world wh
On Wed, Nov 12, 2014 at 10:21 AM, Pedro Martelletto
wrote:
> hi!
>
> the fix consists of disallowing file allocations on directories that
> have been removed (tn_links == 0). failure to enforce such a check can
> lead to the violation of the assumption that removed directories should
> not contain
On Sun, Dec 7, 2014 at 9:47 AM, Jason McIntyre wrote:
> On Sat, Dec 06, 2014 at 09:26:39AM +0001, Jason McIntyre wrote:
>> hi! chasing down netbsd pr 49451:
>>
>> http://marc.info/?l=netbsd-bugs&m=14121109930
>>
>> they've basically added an attribute to the following quote:
>>
>>
Il Sab 21 Ott 2023, 09:37 Luca Di Gregorio ha scritto:
> Host:
> # uname -a
> OpenBSD xxx.my.domain 7.4 GENERIC.MP#1397 amd64
> # dmesg | egrep '(VMX/EPT|SVM/RVI)'
> vmm0 at mainbus0: VMX/EPT
> # vmctl show
>ID PID VCPUS MAXMEM CURMEM TTYOWNERSTATE NAME
> 2 17798 1
Hello,
On my ThinkPad T14s (20XF006JGE), imt(4) touchpad stops working
after resuming from S3 sleep. The only way to get it working again
is to reboot. The three touchpad buttons and the nipple trackpoint
still work without problems. This does not happen when resuming
from S0ix suspend, but I c
Il giorno 21/lug/2012 15:22, "Stuart Henderson" ha
scritto:
>
> On 2012/07/20 14:03, LEVAI Daniel wrote:
> > Hi!
> >
> > It just crashed, didn't do anything fancy with it. I was connected with
> > ssh to the machine when suddenly I got disconnected.
>
> http://marc.info/?l=openbsd-misc&m=134072894
Il giorno 21/lug/2012 17:20, "David Coppa" ha scritto:
>
>
> Il giorno 21/lug/2012 15:22, "Stuart Henderson" ha
scritto:
>
> >
> > On 2012/07/20 14:03, LEVAI Daniel wrote:
> > > Hi!
> > >
> > > It just crashed, didn't d
diff please
On Sat, Aug 25, 2012 at 3:29 AM, X-user wrote:
> Add code to enable boot-time configuration of this device:
>
> file: src/sys/dev/pci/if_iwn.c, from line: 93
> [begin code]
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_100_2 },
> { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_WL_130_1 },
> { PCI_
On Wed, Nov 21, 2012 at 2:57 PM, Bob Beck wrote:
> Dude. There are many old bugs in there to find. Trust me. Start reading
> code instead of shining turds
+1
cheers,
David
On Thu, 24 Jan 2013, ja...@cieti.lv wrote:
> Hello!
>
> If I type r r in console or xterm, like:
>
> $ r r
>
> I get ksh.core. It works on i386 5.2 and amd64 current.
Sure?
I'm on amd64 -current and don't have this bug:
$ r r
rm *orig
rm: *orig: No such file or directory
$
On Tue, Apr 23, 2013 at 4:45 PM, Andreas Bartelt wrote:
> Hi,
>
> revision 1.177 doesn't disable inetd. Fix is attached.
I confirm the issue.
But dunno if the fix below is the right approach...
> I suppose the new behavior should also be documented in
> http://www.openbsd.org/faq/current.html
>
On Mon, May 20, 2013 at 6:15 PM, Alexey E. Suslikov
wrote:
> Mike Larkin azathoth.net> writes:
>
>> You're kidding, right?
>
> Could you guys tell what exactly wrong with FreeBSD/NetBSD approach?
>
Adding some silly workarounds to the kernel for a bug that is a *KVM bug*.
On Tue, Jun 4, 2013 at 3:36 PM, stolendata.net
wrote:
> Perhaps I was being vague, perhaps you didn't read the report through...:
"Power saving support for host ap means that the AP is able to
buffer packets for *clients* in power-save mode. There is nothing to
configure for this."
What part of
> From: Roman
> Date: Wed, Jan 29, 2014 at 12:05 PM
> Subject: ftp(1) progress meter mad
> To: bugs@openbsd.org
>
>
> >Synopsis: output of ftp command is ugly when it reads from pipe
> >Category: user
> >Environment:
> System : OpenBSD 5.5
> Details : OpenBSD 5
On Wed, Jan 29, 2014 at 2:52 PM, David Coppa wrote:
>> From: Roman
>> Date: Wed, Jan 29, 2014 at 12:05 PM
>> Subject: ftp(1) progress meter mad
>> To: bugs@openbsd.org
>>
>>
>> >Synopsis: output of ftp command is ugly when it reads from
> From: David Coppa
> Date: Wed, Jan 29, 2014 at 3:01 PM
> Subject: Re: ftp(1) progress meter mad
> To: bugs@openbsd.org
> Cc: rsg...@ya.ru
>
>
> On Wed, Jan 29, 2014 at 2:52 PM, David Coppa wrote:
> >> From: Roman
> >> Date: Wed, Jan 29, 2014 at 12
On Wed, Jan 29, 2014 at 4:47 PM, Ted Unangst wrote:
> On Wed, Jan 29, 2014 at 08:27, David Coppa wrote:
>> This should be ok:
>
> looks right.
I've committed my fix.
cheers,
David
39 matches
Mail list logo
