[Bug 1898036] [NEW] crash on do-release-upgrade

2020-10-01 Thread Teeedubb
Public bug reported:

Crash occurred when upgrading 18.04.05 via do-release-upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.38
ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CrashDB: ubuntu
Date: Thu Oct  1 22:12:45 2020
InstallationDate: Installed on 2019-04-24 (525 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-10-01 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2020-10-01 22:11:27.147716
 Log time: 2020-10-01 22:11:37.972731
 Log time: 2020-10-01 22:12:44.742132
 Log time: 2020-10-01 22:12:49.200913

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898036

Title:
  crash on do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898036/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1854618] Re: All LEDs flashing on Dualshock 3 controller

2019-12-04 Thread Teeedubb
Hi,

A kernel update was installed today and the lights are now working as
they should be. Not sure if it was because of this report, if it was -
thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854618

Title:
  All LEDs flashing on Dualshock 3 controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1854618] [NEW] All LEDs flashing on Dualshock 3 controller

2019-12-01 Thread Teeedubb
Public bug reported:

Hi,

On Kernel 5.3.0-23-generic all 4 LEDs continuously flash on a paired
Dualshock 3 controller. The expected behaviour is that 1 LED of the 4
light up continuously to indicate which player the controller is
assigned to.

Upgrading to kernel 5.4.1 from the mainline PPA fixes the flashing
lights and only 1 lights up.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-23-generic 5.3.0-23.25
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  blaster1050 F kodi-x11
 /dev/snd/pcmC0D7p:   blaster1050 F...m kodi-x11
Date: Sun Dec  1 21:16:22 2019
InstallationDate: Installed on 2019-11-07 (24 days ago)
InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: HARDKERNEL ODROID-H2
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=0d6be0de-27a0-429d-84b3-978a7349e3da ro net.ifnames=0 biosdevname=0 
i915.fastboot=1 video=HDMI-A-1:1920x1080@60D video=HDMI-A-2:1920x1080@60D 
drm.edid_firmware=HDMI-A-1:edid/edid-rxv473.bin,HDMI-A-2:edid/edid-mu7000.bin 
quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-23-generic N/A
 linux-backports-modules-5.3.0-23-generic  N/A
 linux-firmware1.183.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.13
dmi.board.asset.tag: Default string
dmi.board.name: ODROID-H2
dmi.board.vendor: HARDKERNEL
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd08/22/2019:svnHARDKERNEL:pnODROID-H2:pvr1.0:rvnHARDKERNEL:rnODROID-H2:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: ODROID-H2
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: HARDKERNEL

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1854618

Title:
  All LEDs flashing on Dualshock 3 controller

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854618/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2019-11-20 Thread Teeedubb
Hi,

I am experiencing the same issue with Kodi 18.5 and Xubuntu 19.10 with
similar stack traces to joe-yasi. Is there anyway to install the updated
package via Ubuntu updates?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833479

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777238] Re: video lag - Every 5 seconds a freeze frame when playing video of any source

2019-11-07 Thread Teeedubb
I can't see a option to edit posts, but the gpu I am using is an Intel
from a j4105 CPU

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777238

Title:
  video lag - Every 5 seconds a freeze frame when playing video of any
  source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1777238] Re: video lag - Every 5 seconds a freeze frame when playing video of any source

2019-11-06 Thread Teeedubb
Hi,

I haven't read through this entire report, but I stumbled across it when
searching for 'stutter every 5 sexonds'. I too had the issue, across
many distros + compositors with Kodi (I didn't really test anything
else). I have enabled the tear free option in a xorg.conf and the issue
has disappeared. Might be worth you guys trying.

https://askubuntu.com/questions/1066722/intel-screen-tearing-
ubuntu-18-04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777238

Title:
  video lag - Every 5 seconds a freeze frame when playing video of any
  source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1554586] Re: plymouth disappear, only the animated logo stays

2017-02-07 Thread Teeedubb
Any updates on this? I'm experiening the same issue as Piotr - The logo
is initially displayed, but when the animation for the "dots" starts,
the logo disappears and then only the dots are displayed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554586

Title:
  plymouth disappear, only the animated logo stays

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1554586/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1278012] Re: tearing with vsync enabled

2014-03-04 Thread Teeedubb
Same with a nvidia 660ti with 304, 331, 334 nvidia drivers on x64 14.04
+ xserver-xorg-core_1.14.5-1ubuntu1_amd64. Downgrading to
2:1.14.5-1ubuntu gets rid of the tearing. Running xbmc in its own
xsession with alsa. Problem only occours in XBMC.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1278012

Title:
  tearing with vsync enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1278012/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1244411] Re: Unable to disable wake from suspend on USB device.

2013-10-30 Thread Teeedubb
Hi

Thanks for the info about the bios update, but unfortunatley that does
not help. What I did was fresh boot the pc after bios update (wake on kb
+ mouse disabled) , checked that wakeup was disabled as above (it was),
suspend the pc via xbmc or pm-suspend. Pressing any button on the
iPazzPort rf wireless kb will wake the htpc. I have also tried disabling
wake on every device to no avail (see link for more detail):

http://forum.xbmc.org/showthread.php?tid=174019

Output of the requested command:

xbmc ~ $  sudo dmidecode -s bios-version  sudo dmidecode -s bios-release-date
F21
08/12/2013

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244411

Title:
  Unable to disable wake from suspend on USB device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1244411] Re: Unable to disable wake from suspend on USB device.

2013-10-25 Thread Teeedubb
** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244411

Title:
  Unable to disable wake from suspend on USB device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1244411] Re: Unable to disable wake from suspend on USB device.

2013-10-25 Thread Teeedubb
** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244411

Title:
  Unable to disable wake from suspend on USB device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1244411] [NEW] Unable to disable wake from suspend on USB device.

2013-10-24 Thread Teeedubb
Public bug reported:

I am unable to disable wake from suspend on USB devices, even though
everything apperas setup correctly and the following information works
with another distribution, Openelec. The system is running minimal
ubuntu 13.10 x64 and I am using a udev rule to disable wakeup.

The device I am trying to disable is a wireless keyboard:

Bus 003 Device 002: ID 0c45:7000 Microdia

Wakeup is disabled:

xbmc@blaster:~$ grep 7000 /sys/bus/usb/devices/*/idProduct
/sys/bus/usb/devices/3-1/idProduct:7000
xbmc@blaster:~$ cat /sys/bus/usb/devices/3-1/power/wakeup
disabled

Udev rule:

xbmc@blaster:~$ cat /etc/udev/rules.d/disable-wakeup.rules
SUBSYSTEM==usb, ATTRS{idVendor}==0471, ATTRS{idProduct}==2093, 
RUN+=/bin/sh -c 'echo enabled  /sys$env{DEVPATH}/../power/wakeup'


Pressing any key on the keyboard will wake my pc from s3 suspend.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-12-generic 3.11.0-12.19
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
Uname: Linux 3.11.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  xbmc   4060 F xbmc.bin
 /dev/snd/pcmC0D7p:   xbmc   4060 F...m xbmc.bin
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Fri Oct 25 07:28:38 2013
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=5c99d0a0-eb2f-456c-b8f3-51a6037d2850 ro splash quiet nomodeset 
video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic  N/A
 linux-firmware 1.116
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F18
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z77-D3H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF18:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug saucy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244411

Title:
  Unable to disable wake from suspend on USB device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1244411/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1244411] Re: Unable to disable wake from suspend on USB device.

2013-10-24 Thread Teeedubb
** Description changed:

  I am unable to disable wake from suspend on USB devices, even though
  everything apperas setup correctly and the following information works
  with another distribution, Openelec. The system is running minimal
  ubuntu 13.10 x64 and I am using a udev rule to disable wakeup.
  
  The device I am trying to disable is a wireless keyboard:
  
  Bus 003 Device 002: ID 0c45:7000 Microdia
  
  Wakeup is disabled:
  
  xbmc@blaster:~$ grep 7000 /sys/bus/usb/devices/*/idProduct
  /sys/bus/usb/devices/3-1/idProduct:7000
  xbmc@blaster:~$ cat /sys/bus/usb/devices/3-1/power/wakeup
  disabled
  
  Udev rule:
  
  xbmc@blaster:~$ cat /etc/udev/rules.d/disable-wakeup.rules
- SUBSYSTEM==usb, ATTRS{idVendor}==0471, ATTRS{idProduct}==2093, 
RUN+=/bin/sh -c 'echo enabled  /sys$env{DEVPATH}/../power/wakeup'
- 
+ SUBSYSTEM==usb, ATTRS{idVendor}==0471, ATTRS{idProduct}==2093, 
RUN+=/bin/sh -c 'echo disabled  /sys$env{DEVPATH}/../power/wakeup'
  
  Pressing any key on the keyboard will wake my pc from s3 suspend.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  xbmc   4060 F xbmc.bin
-  /dev/snd/pcmC0D7p:   xbmc   4060 F...m xbmc.bin
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  xbmc   4060 F xbmc.bin
+  /dev/snd/pcmC0D7p:   xbmc   4060 F...m xbmc.bin
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Fri Oct 25 07:28:38 2013
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  MarkForUpload: True
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=5c99d0a0-eb2f-456c-b8f3-51a6037d2850 ro splash quiet nomodeset 
video=uvesafb:mode_option=1920x1080-24,mtrr=3,scroll=ywrap
  RelatedPackageVersions:
-  linux-restricted-modules-3.11.0-12-generic N/A
-  linux-backports-modules-3.11.0-12-generic  N/A
-  linux-firmware 1.116
+  linux-restricted-modules-3.11.0-12-generic N/A
+  linux-backports-modules-3.11.0-12-generic  N/A
+  linux-firmware 1.116
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F18
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-D3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF18:bd08/21/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

** Description changed:

  I am unable to disable wake from suspend on USB devices, even though
  everything apperas setup correctly and the following information works
  with another distribution, Openelec. The system is running minimal
  ubuntu 13.10 x64 and I am using a udev rule to disable wakeup.
  
  The device I am trying to disable is a wireless keyboard:
  
  Bus 003 Device 002: ID 0c45:7000 Microdia
  
  Wakeup is disabled:
  
  xbmc@blaster:~$ grep 7000 /sys/bus/usb/devices/*/idProduct
  /sys/bus/usb/devices/3-1/idProduct:7000
  xbmc@blaster:~$ cat /sys/bus/usb/devices/3-1/power/wakeup
  disabled
  
  Udev rule:
+ xbmc@blaster:~$ cat /etc/udev/rules.d/disable-wakeup.rules
+ SUBSYSTEM==usb, ATTRS{idVendor}==0c45, ATTRS{idProduct}==7000, 
RUN+=/bin/sh -c 'echo disabled  /sys$env{DEVPATH}/../power/wakeup'
  
- xbmc@blaster:~$ cat /etc/udev/rules.d/disable-wakeup.rules
- SUBSYSTEM==usb, ATTRS{idVendor}==0471, ATTRS{idProduct}==2093, 
RUN+=/bin/sh -c 'echo disabled  /sys$env{DEVPATH}/../power/wakeup'
  
  Pressing any key on the keyboard will wake my pc from s3 suspend.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image-3.11.0-12-generic 3.11.0-12.19
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  xbmc   4060 F xbmc.bin
   /dev/snd/pcmC0D7p:   xbmc   4060 F...m xbmc.bin
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  Date: Fri 

[Bug 771807] Re: package gdm 2.32.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128

2011-04-27 Thread Teeedubb
-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771807

Title:
  package gdm 2.32.1-0ubuntu3 failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 128

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 771807] [NEW] package gdm 2.32.1-0ubuntu3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 128

2011-04-27 Thread Teeedubb
Public bug reported:

Binary package hint: gdm

ubtntu 11.04 natty x64, all updates as of 27.4.11

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: gdm 2.32.1-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AptOrdering:
 gdm-guest-session: Purge
 gdm: Purge
Architecture: amd64
Date: Wed Apr 27 18:31:09 2011
ErrorMessage: subprocess installed post-removal script returned error exit 
status 128
SourcePackage: gdm
Title: package gdm 2.32.1-0ubuntu3 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gdm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package natty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771807

Title:
  package gdm 2.32.1-0ubuntu3 failed to install/upgrade: subprocess
  installed post-removal script returned error exit status 128

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 493811] Re: gnome-system-log uses 100%+ Cpu usage

2011-03-10 Thread Teeedubb
I was experiencing these issues to with ubuntu 10.04.2 x64. Running
gnome-system-log with root privileges has seems to fix the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/493811

Title:
  gnome-system-log uses 100%+ Cpu usage

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 573477] Re: Mdadm array fails to assemble on boot.

2010-12-13 Thread Teeedubb
I know that this bug doesnt exist with 10.04.1 with an array constructed
in 10.04.1 using mdadm.

I gave up on this bug as it wasnt a show stopper (server was rarely
rebooted), but have made some observations during the new build that
might shed some light on this. I used the palimpest disk utility to
construct my array and Im 99% sure I did previously too, though this
time I noticed some quirks, like the utility being unable to expand an
array built by mdadm or the disk utility (saying the device wasnt big
enough to add, but it is identical to the other drives.), mdadm unable
to assesmble a array made by the disk utility while the disk utility was
able to and on boot the disk utility has the array as started but
degraded (stopping/starting the array fixes this). The array would work
store data and mount without issue if constructed and stopped/started
using the disk utility.

This got me thinking that maybe this was somehow related to the issues I
was having previously. Anyone else assemble their arrays with the disk
utility? Just putting it out there

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/573477

Title:
  Mdadm array fails to assemble on boot.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 573477] Re: Mdadm array fails to assemble on boot.

2010-05-05 Thread teeedubb
I spotted this error while installing lucid lynx and mdadm on another
machine:

Setting up mdadm (2.6.7.1-1ubuntu15) ...
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: 
/dev/MAKEDEV: not found
failed.
Generating mdadm.conf... done.
 Removing any system startup links for /etc/init.d/mdadm-raid ...

Could this have something to do with the array not starting?

Here is the complete transcript of the install:

The following NEW packages will be installed:
  mdadm postfix
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,642kB of archives.
After this operation, 4,248kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://archive.ubuntu.com/ubuntu/ lucid/main mdadm 2.6.7.1-1ubuntu15 
[239kB]
Get:2 http://archive.ubuntu.com/ubuntu/ lucid/main postfix 2.7.0-1 [1,403kB]
Fetched 1,642kB in 8s (200kB/s)
Preconfiguring packages ...
Selecting previously deselected package mdadm.
(Reading database ... 149165 files and directories currently installed.)
Unpacking mdadm (from .../mdadm_2.6.7.1-1ubuntu15_amd64.deb) ...
Selecting previously deselected package postfix.
Unpacking postfix (from .../postfix_2.7.0-1_amd64.deb) ...
Processing triggers for ureadahead ...
Processing triggers for doc-base ...
Processing 26 changed 1 added doc-base file(s)...
Registering documents with scrollkeeper...
Processing triggers for man-db ...
Processing triggers for ufw ...
Setting up mdadm (2.6.7.1-1ubuntu15) ...
Generating array device nodes... /var/lib/dpkg/info/mdadm.postinst: 170: 
/dev/MAKEDEV: not found
failed.
Generating mdadm.conf... done.
 Removing any system startup links for /etc/init.d/mdadm-raid ...
update-initramfs is disabled since running on read-only media
update-rc.d: warning: mdadm start runlevel arguments (2 3 4 5) do not match LSB 
Default-Start values (S)
update-rc.d: warning: mdadm stop runlevel arguments (0 1 6) do not match LSB 
Default-Stop values (0 6)
 * Starting MD monitoring service mdadm --monitor[ OK ] 

Setting up postfix (2.7.0-1) ...
Adding group `postfix' (GID 123) ...
Done.
Adding system user `postfix' (UID 115) ...
Adding new user `postfix' (UID 115) with group `postfix' ...
Not creating home directory `/var/spool/postfix'.
Creating /etc/postfix/dynamicmaps.cf
Adding tcp map entry to /etc/postfix/dynamicmaps.cf
Adding group `postdrop' (GID 124) ...
Done.
setting myhostname: ubuntu
setting alias maps
setting alias database
mailname is not a fully qualified domain name.  Not changing /etc/mailname.
setting destinations: ubuntu, localhost.localdomain, , localhost
setting relayhost: 
setting mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
setting mailbox_size_limit: 0
setting recipient_delimiter: +
setting inet_interfaces: all
/etc/aliases does not exist, creating it.
WARNING: /etc/aliases exists, but does not have a root alias.

Postfix is now set up with a default configuration.  If you need to make 
changes, edit
/etc/postfix/main.cf (and others) as needed.  To view Postfix configuration
values, see postconf(1).

After modifying main.cf, be sure to run '/etc/init.d/postfix reload'.

Running newaliases
 * Stopping Postfix Mail Transport Agent postfix [ OK ] 
 * Starting Postfix Mail Transport Agent postfix [ OK ] 

Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
ubu...@ubuntu:~$

-- 
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 573477] [NEW] Mdadm array fails to assemble on boot.

2010-05-02 Thread teeedubb
Public bug reported:

Binary package hint: mdadm

On boot I receive a message stating 'the disk for/mnt/md0 is not ready
yet or not present. Continue to wait; or Press S to skip mount or M for
manual recovery'. If i press M and try 'mount -a' it states that
'special device /dev/md0 does not exist'. If I try 'mdadm --assemble
--scan' it states 'no devices found for /dev/md0'. If I skip the
mounting of the array, and start the array then mount it through
palimpsest everything mounts as should be (devices in array and mount
location).

Output of 'mdadm -D /dev/md0'

/dev/md0:
Version : 01.02
  Creation Time : Mon Nov 16 12:30:36 2009
 Raid Level : raid5
 Array Size : 1465151424 (1397.28 GiB 1500.32 GB)
  Used Dev Size : 976767616 (931.52 GiB 1000.21 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent

  Intent Bitmap : Internal

Update Time : Sun May  2 15:58:29 2010
  State : active
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

 Layout : left-symmetric
 Chunk Size : 64K

   Name : :raid5
   UUID : 02bcfe3b:44fc949f:f5f7e481:a421a2c0
 Events : 55496

Number   Major   Minor   RaidDevice State
   0   8   490  active sync   /dev/sdd1
   1   8   331  active sync   /dev/sdc1
   2   8   172  active sync   /dev/sdb1
   4   813  active sync   /dev/sda1


Contents of /etc/mdadm/mdadm.conf:

# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST system

# instruct the monitoring daemon where to send mail alerts
MAILADDR server

# definitions of existing MD arrays
ARRAY /dev/md0 level=raid5 metadata=1.2 num-devices=4 
UUID=02bcfe3b:44fc949f:f5f7e481:a421a2c0 name=md0

# This file was auto-generated on Sat, 01 May 2010 18:15:04 +1000
# by mkconf $Id$


Contents of /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
# file system mount point   type  options   dump  pass
proc/proc   procnodev,noexec,nosuid 0   0
# / was on /dev/sda1 during installation
UUID=906694f9-9425-4ae3-88cc-bd9f4161846b /   ext4
errors=remount-ro 0   1
# swap was on /dev/sda5 during installation
UUID=01cb5d34-e4ac-4329-95c1-e9396a414a28 noneswapsw
  0   0
#mdadm array
/dev/md0/mnt/md0autodefaults0   0

** Affects: mdadm (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 561390] Re: LVM - /var failed to mount during boot

2010-05-01 Thread teeedubb
I seem to be having a similar issue, although with a mdadm raid 5 array.
I get the screen stating 'the disk for/mnt/md0 is not ready yet or not
present'. If i press M and try 'mount -a' it states that 'special device
/dev/md0 does not exist'. If I try 'mdadm --assemble --scan' it states
'no devices found for /dev/md0'. If I skip the mounting of the array,
and start the array then mount it through palimpset everything mounts as
should be (devices in array and mount location).

I have added Scott's repositories and upgraded mountall to no avail. The
output of 'dpkg-query -W dmsetup' is 'dmsetup  2:1.02.39-1ubuntu4'. This
seems different from the version I should have. I have included my
/var/log/boot.log. I will attach the udev file from the same directory
in my next post (I cant attach two files to this post)


** Attachment added: boot.log
   http://launchpadlibrarian.net/46916526/boot.log

-- 
LVM - /var failed to mount during boot
https://bugs.launchpad.net/bugs/561390
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs