[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-08-07 Thread dx9s
FWIW: *THEY* (including Steffen Joeris) thinks the problem is fixed... and that all web documents are to be owned by root.. (mind you I make the config file owned by root and log files and so forth) .. or that ONE person that needs to run a script but they can't place it anywhere because the

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-08-26 Thread dx9s
I think this should work (however in my case, I compiled from source): Download '*0.6.2-1ubuntu1_i386.deb' files (as listed below in the deb -i) from launchpad (might need current version on the purge statements) % sudo apt-get purge libapache2-mod-suphp % sudo apt-get purge suphp-common % deb

RE: [Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-09-03 Thread dx9s
and after looking at the changes.. it's really less secure. --Doug From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 27 Aug 2008 14:24:43 + Subject: [Bug 253268] Re: php5-cgi not working with suphp in Hardy dx9s: Where did this deb come from

[Bug 282751] Re: Winbind package does not provide PAM configuration

2009-09-03 Thread dx9s
I tried that file (winbind) that Edgar provided in the /usr/share/pam- configs and it re-wrote the /etc/pam.d/ files -- I have yet to test login to the console from the Windows AD. -- Winbind package does not provide PAM configuration https://bugs.launchpad.net/bugs/282751 You received this bug

[Bug 282751] Re: Winbind package does not provide PAM configuration

2009-09-03 Thread dx9s
was able to log in to machine (console and ssh) using AD creds... Now if I can figure out the strange things in the log file ... (doesn't show on other server with slightly older samba but very similar configuration) -- Winbind package does not provide PAM configuration

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2009-09-10 Thread dx9s
I know this isn't an issue with the distribution.. but a problem with the maintainer... Thanks Canonical for your support anyways. It is just a little strange and I need to test what Piotr is referring to in Jaunty (I've been staying away from dist ugprades as the production machine I have

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-08-07 Thread dx9s
in folder to work) -- this is a serious break-age of suphp --dx9s (Doug) ** CVE added: http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=2008-1614 -- php5-cgi not working with suphp in Hardy https://bugs.launchpad.net/bugs/253268 You received this bug notification because you are a member

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-08-07 Thread dx9s
FWIW: *THEY* (including Steffen Joeris) thinks the problem is fixed... and that all web documents are to be owned by root.. (mind you I make the config file owned by root and log files and so forth) .. or that ONE person that needs to run a script but they can't place it anywhere because the

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-08-26 Thread dx9s
I think this should work (however in my case, I compiled from source): Download '*0.6.2-1ubuntu1_i386.deb' files (as listed below in the deb -i) from launchpad (might need current version on the purge statements) % sudo apt-get purge libapache2-mod-suphp % sudo apt-get purge suphp-common % deb

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-08-26 Thread dx9s
download the link above * (technically unchanged) .deb files with older code made on a Hardy machine (70.1 KiB, application/x-debian-package) (should be suphp-common) and libapache2-mod-suphp from here! ** Attachment added: libapache2-mod-suphp_0.6.2-1ubuntu1_i386.deb

[Bug 191027] Re: Failed to connect stream: Invalid argument

2008-10-05 Thread dx9s
I was having same problem with the developer branch of intrepid... 1) tried the reinstalling of ubuntu-desktop ... no-go... 2) restarting the pulseaudio server works (and an .xinitrc makes it more painless-of-a-workaround) 3) skip'ed installing the update alsa packages (so can't comment on

[Bug 191027] Re: Failed to connect stream: Invalid argument

2008-10-05 Thread dx9s
update: fixed the drum sounds in gdm ... seems like it is influenced by a bad .asoundrc/.aroundrc.asoundconf (which points to pulse ... and no pulse server when gdm is at the login screen) ... removed the .asoundrc / .asoundrc.asoundconf from root's home dir remove the .asoundrc /

[Bug 191027] Re: Failed to connect stream: Invalid argument

2008-10-06 Thread dx9s
Leon .. are you suggesting there should be a system pulseaudio server (running as root / system wide kind of thing?) I'll ask the question another way (to any developers)... what is the start-up process for pulseaudio ? when should it start (I saw the /etc/init.d/ and /etc/rc?.d/ for pulseaudio)

[Bug 191027] Re: Failed to connect stream: Invalid argument

2008-10-07 Thread dx9s
Leon... that's the same as what others are doing... restarting the pulseaudio server in your user space... that also works for me... as a workaround. but in my case, I found removing the .asoundrc* (or 'asoundconf set- pulseaudio') to create ones pointing to pulseaudio server in a special way --

RE: [Bug 253268] Re: php5-cgi not working with suphp in Hardy

2008-09-03 Thread dx9s
and after looking at the changes.. it's really less secure. --Doug From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, 27 Aug 2008 14:24:43 + Subject: [Bug 253268] Re: php5-cgi not working with suphp in Hardy dx9s: Where did this deb come from

[Bug 282751] Re: Winbind package does not provide PAM configuration

2009-09-03 Thread dx9s
I tried that file (winbind) that Edgar provided in the /usr/share/pam- configs and it re-wrote the /etc/pam.d/ files -- I have yet to test login to the console from the Windows AD. -- Winbind package does not provide PAM configuration https://bugs.launchpad.net/bugs/282751 You received this bug

[Bug 282751] Re: Winbind package does not provide PAM configuration

2009-09-03 Thread dx9s
was able to log in to machine (console and ssh) using AD creds... Now if I can figure out the strange things in the log file ... (doesn't show on other server with slightly older samba but very similar configuration) -- Winbind package does not provide PAM configuration

[Bug 836349] [NEW] package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build 2.6.38-10

2011-08-28 Thread dx9s
Public bug reported: Need to upgrade to newer kernel.. I know 2.6.39 supports USB 3.0 hubs.. but only have 2.6.38-10 from Ubuntu (hopefully -10 backports that support!?) .. so attempted to install it and got nvidia dkms build fail on that kernel... Guessing a newer current will be required?!

[Bug 836349] Re: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build 2.6.38-10

2011-08-28 Thread dx9s
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/836349 Title: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build 2.6.38-10 To

[Bug 627022] Re: package nvidia-current 195.36.24-0ubuntu1~10.04 failed to install/upgrade: nvidia-current kernel module failed to build (nv.c:417: error: unknown field ‘ioctl’ specified in initialize

2011-08-29 Thread dx9s
I also reported a pretty much duplicate issue with this in #836349 ... looks like this has been ongoing for a while and is stuck on kernel API call changes... I was trying to upgrade to Ubuntu's kernel 2.6.38-10 (really need 2.6.39 as that is known to have USB 3.0 **HUB** support 38-10 might have

[Bug 292606] Re: dkms - error when installing custom kernel

2008-11-11 Thread dx9s
I have the same problem and I came to same conclusion that it was nvidia-common ... upon trying to figure out what package it came from... it comes from nvidia-common (quite simple). The weird thing is I didn't have that package installed.. so I installed it (and it also flagged other modaliases

[Bug 253268] Re: php5-cgi not working with suphp in Hardy

2009-09-10 Thread dx9s
I know this isn't an issue with the distribution.. but a problem with the maintainer... Thanks Canonical for your support anyways. It is just a little strange and I need to test what Piotr is referring to in Jaunty (I've been staying away from dist ugprades as the production machine I have

[Bug 561581] [NEW] WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-12 Thread dx9s
Public bug reported: Looks like lots of others with this, but not exact hardware... so figured report separate report. ProblemType: KernelOops DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-20-generic 2.6.32-20.29 Regression: Yes Reproducible: No ProcVersionSignature: Ubuntu

[Bug 561581] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-12 Thread dx9s
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/43929996/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/43929997/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt

[Bug 563103] [NEW] WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-14 Thread dx9s
Public bug reported: SERIOUSLY... I had a Serious Problem occur WHILE reporting a serious problem!!! this is really annoying and not sure where it is happening .. and while typing.. another serious problem just pop'ed up! time to roll back to older kernel! ProblemType: KernelOops DistroRelease:

[Bug 563103] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-14 Thread dx9s
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/44159425/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/44159426/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt

[Bug 563109] [NEW] WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-14 Thread dx9s
Public bug reported: 3rd serious problem in a row while in middle of reporting the first serious problem... I hope somebody knows there is an issue with sortirq ProblemType: KernelOops DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-20-generic 2.6.32-20.29 Regression: Yes Reproducible:

[Bug 563109] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-14 Thread dx9s
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/44159830/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/44159831/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt

[Bug 563107] [NEW] WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-14 Thread dx9s
Public bug reported: 2nd oops while reporting a problem .. (aka had a serious problem while reporting a serious problem.. and a 3rd one came up as well) -- will report that ProblemType: KernelOops DistroRelease: Ubuntu 10.04 Package: linux-image-2.6.32-20-generic 2.6.32-20.29 Regression: Yes

[Bug 563107] Re: WARNING: at /build/buildd/linux-2.6.32/kernel/softirq.c:143 local_bh_enable_ip+0x61/0x90()

2010-04-14 Thread dx9s
** Attachment added: AlsaDevices.txt http://launchpadlibrarian.net/44159669/AlsaDevices.txt ** Attachment added: BootDmesg.txt http://launchpadlibrarian.net/44159670/BootDmesg.txt ** Attachment added: Card0.Amixer.values.txt

[Bug 1642405] [NEW] lxd lxd.db Unsupported suffix

2016-11-16 Thread dx9s
be a problem in that code branch as well. Just thought somebody would want to know that this simple-to-make typo (M instead of MB) has completely made the container unusable. --Doug (dx9s) ** Affects: lxd (Ubuntu) Importance: Undecided Status: New -- You received this bug

[Bug 1642405] Re: lxd lxd.db Unsupported suffix

2016-11-18 Thread dx9s
Thanks for the feedback. I probably didn't do an exhaustive search for this known issue. Thanks for the sqlite3 syntax. FWIW: LXD 2 is an amazing implementation for working with containers. Thanks for your work! --Doug (dx9s) -- You received this bug notification because you are a member