Displaying 7 results from an estimated 7 matches for "procenviron".
2010 Oct 18
0
[Bug 662435] [NEW] megatec_usb driver stopped working after upgrade from 8.04 to 10.04
...SION 2.4.3 not
> 2.2.2.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 10.04
> Package: nut 2.2.2-6ubuntu1
> ProcVersionSignature: Ubuntu 2.6.32-25.44-server 2.6.32.21+drm33.7
> Uname: Linux 2.6.32-25-server x86_64
> Architecture: amd64
> Date: Mon Oct 18 01:29:57 2010
> ProcEnviron:
> LANG=de_DE.UTF-8
> SHELL=/bin/bash
> SourcePackage: nut
>
>
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/nut/+bug/662435/+subscribe
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <...
2017 Jun 29
1
setting gfid on .trashcan/... failed - total outage
...mvol1.pid -S
/var/run/gluster/5e23d9709b37ac7877720ac3986c48bc.socket --brick-name
/brick1/mvol1 -l /var/log/glusterfs/bricks/brick1-mvol1.log
--xlator-option
*-posix.glusterd-uuid=056fb1db-9a49-422d-81fb-94e1881313fd --brick-port
49152 --xlator-option mvol1-server.listen-port=49152
ProcCwd: /
ProcEnviron:
LANGUAGE=en_GB:en
[ 14:48:52 ] - root at gl-master-03 ~ $
>
--
Dietmar Putz
3Q GmbH
Wetzlarer Str. 86
D-14482 Potsdam
Telefax: +49 (0)331 / 2797 866 - 1
Telefon: +49 (0)331 / 2797 866 - 8
Mobile: +49 171 / 90 160 39
Mail: dietmar.putz at 3qsdn.com
2012 Feb 01
6
[Bug 45517] New: [GTX 580] X seems to hang a login prompt -- PFIFO errors in dmesg
...02 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 003: ID 099a:7202 Zippy Technology Corp.
ProcEnviron:
LC_CTYPE=en_GB.UTF-8
LC_COLLATE=en_GB.UTF-8
LANG=en_GB.UTF-8
LC_MESSAGES=en_GB.UTF-8ProcKernelCmdLine:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-12-generic
root=UUID=375e3b8f-01ec-41de-80ee-6ab3210f6988 ro quiet splash nolapic_timer
vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to precise on 2012-...
2011 Feb 17
8
[Bug 34371] New: [natty] Video corruption on kernel 2.6.38-1-generic (and on -3) and nVidia Corporation GT216 [GeForce GT 230M] (rev a2)
...d: Yes, recently upgraded Log time: 2010-11-25 14:33:02.550411
DistroCodename: natty
DistroVariant: ubuntu
GraphicsCard: Subsystem: Sony Corporation Device [104d:905e]
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: Sony Corporation VPCCW1FFX
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic
root=UUID=f415c990-a34d-451b-b69c-2070c5d53e47 ro nouveau.noaccel=1 quiet
splash vt.handoff=7
Renderer: Unknown
SourcePackage: xorg
dmi.bios.date: 09/22/2009
dmi.bios.vendor: American Megatrends I...
2011 Mar 21
11
[Bug 35514] New: Black screen with nouveau on a GeForce 8600M GT, either LiveCD or fresh install
...un Feb 6 00:58:13 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus: vboxhost, 4.0.2: added
GraphicsCard: Subsystem: Dell Device [1028:0228]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110131)
MachineType: Dell Inc. Vostro 1500
ProcEnviron:
LANGUAGE=fr_FR.UTF-8:fr:en_GB:en
LANG=fr_FR.UTF-8
LC_MESSAGES=fr_FR.utf8ProcKernelCmdLine:
BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-generic
root=UUID=55a88c4e-93f6-4ba7-aeae-9104bddc2682 ro nomodeset
SourcePackage: xserver-xorg-video-nouveau
dmi.bios.date: 04/21/2008
dmi.bios.vendor: Dell Inc.
dmi.bio...
2017 Jun 29
0
setting gfid on .trashcan/... failed - total outage
On Wed, 2017-06-28 at 14:42 +0200, Dietmar Putz wrote:
> Hello,
>
> recently we had two times a partial gluster outage followed by a total?
> outage of all four nodes. Looking into the gluster mailing list i found?
> a very similar case in?
> http://lists.gluster.org/pipermail/gluster-users/2016-June/027124.html
If you are talking about a crash happening on bricks, were you
2017 Jun 28
2
setting gfid on .trashcan/... failed - total outage
Hello,
recently we had two times a partial gluster outage followed by a total
outage of all four nodes. Looking into the gluster mailing list i found
a very similar case in
http://lists.gluster.org/pipermail/gluster-users/2016-June/027124.html
but i'm not sure if this issue is fixed...
even this outage happened on glusterfs 3.7.18 which gets no more updates
since ~.20 i would kindly ask