[Desktop-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-25 Thread CoderGuy
While it's obviously not a real fix, As I don't use chrome as my primary
browser, simply regenerating my ~/.config/google-chrome/ directory
resolved this issue. Others may not have this option.

Question 1 : What is it about the Mesa upgrade that kills chrome but not 
Firefox?
Question 2 : Is there a less nuclear fix than wiping the Chrome settings? e.g. 
Deleting just the ShaderCache or GrShaderCache directories?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604

Title:
  After mesa upgrades, Chrome won't show graphics

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There is a bypass listed in that article.  Not sure if this is an
  issue with mesa or Chrome or specific machine graphics or an
  interaction between them.

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


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2019-08-21 Thread CoderGuy
@Gunnar,

I've tested on my main PC.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2019-08-16 Thread CoderGuy
@Gunnar,

I've just verified the package in the PPA and like Simon I can say that
it resolves the issue on LiDE 200 devices. I made 10 scans and the bar
was not present in any of the images.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish

2019-08-10 Thread CoderGuy
I have a device, could you share a link to the PPA?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459

Title:
  genesys_gl847 scanners produce a black band in scanned images on
  Ubuntu 17.10+,  18.04 LTS and 18.10 Cosmic cuttlefish

Status in sane-backends:
  Unknown
Status in sane-backends package in Ubuntu:
  In Progress
Status in sane-backends source package in Bionic:
  In Progress
Status in sane-backends source package in Disco:
  In Progress
Status in sane-backends package in Debian:
  Unknown

Bug description:
  [Impact]

  When using a Genesys GL847 scanner, the documents get disfigured by a
  discolored bar. The proposed uploads should fix the issue. They are
  available in this PPA:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends

  [Test case]

  1. Install the libsane (libsane1 in bionic), libsane-common
 and sane-utils packages from {bionic,disco]-proposed.

  2. Use an affected device to scan, and find that the issue is
 no longer present.

  [Regression risk]

  Upstream commit, focused bug fix => low regression risk

  [Original description]

  On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
  black band on scanned image. The scanner is Canon CanoScan LIDE100.
  Libsane version is 1.0.27-1~experimental2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1803885] Re: Lenovo R60 screen corrupt immediately after install

2019-03-31 Thread CoderGuy
For future reference (probably my own), if anyone else has this issue.

Although the problem doesn't entirely go away. There is still some
strange artifacting and ocassionally black foreground in windows. Most
likely memory corruption, as a reboot cures it.

In /etc/gdm3/custom.conf change the line
[daemon]
WaylandEnable=true
to 
WaylandEnable=false

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1803885

Title:
  Lenovo R60 screen corrupt immediately after install

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  Version : Ubuntu 18.04.1 LTS

  Immediately after the install completes. The computer restarts to a
  corrupt login screen.

  Hardware : Lenovo R60
  Video : 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] RV515/M54 [Mobility Radeon X1400]

  Xorg.log

  AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
  AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
  ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
  MULLINS, KAVERI, HAWAII
  [13.133] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [13.133] (II) FBDEV: driver for framebuffer: fbdev
  [13.133] (II) VESA: driver for VESA chipsets: vesa
  [13.135] (II) [KMS] drm report modesetting isn't supported.
  [13.135] (EE) open /dev/dri/card0: No such file or directory
  [13.135] (WW) Falling back to old probe method for modesetting
  [13.135] (EE) open /dev/dri/card0: No such file or directory
  [13.135] (II) Loading sub module "fbdevhw"
  [13.135] (II) LoadModule: "fbdevhw"
  [13.136] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  [13.137] (II) Module fbdevhw: vendor="X.Org Foundation"
  [13.137]compiled for 1.19.6, module version = 0.0.2
  [13.137]ABI class: X.Org Video Driver, version 23.0
  [13.137] (**) FBDEV(2): claimed PCI slot 1@0:0:0
  [13.137] (II) FBDEV(2): using default device
  [13.137] (WW) Falling back to old probe method for vesa
  [13.137] (EE) Screen 0 deleted because of no matching config section.
  [13.137] (II) UnloadModule: "radeon"
  [13.137] (EE) Screen 0 deleted because of no matching config section.
  [13.137] (II) UnloadModule: "modesetting"
  [13.138] (II) FBDEV(0): Creating default Display subsection in Screen 
section
  "Default Screen Section" for depth/fbbpp 24/32
  [13.138] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32

  After some digging, on another computer, adding nomodeset to the
  kernal startup parameters helps. Edited /etc/default/grub

  GRUB_CMDLINE_LINUX="nomodeset"

  $update-grub
  provides a usable but degraded session. 

  The screen resolution is 1400x1050.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1803885] Re: Lenovo R60 screen corrupt immediately after install

2019-03-31 Thread CoderGuy
Anybody got a solution for this?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1803885

Title:
  Lenovo R60 screen corrupt immediately after install

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  Version : Ubuntu 18.04.1 LTS

  Immediately after the install completes. The computer restarts to a
  corrupt login screen.

  Hardware : Lenovo R60
  Video : 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] RV515/M54 [Mobility Radeon X1400]

  Xorg.log

  AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
  AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
  ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
  MULLINS, KAVERI, HAWAII
  [13.133] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [13.133] (II) FBDEV: driver for framebuffer: fbdev
  [13.133] (II) VESA: driver for VESA chipsets: vesa
  [13.135] (II) [KMS] drm report modesetting isn't supported.
  [13.135] (EE) open /dev/dri/card0: No such file or directory
  [13.135] (WW) Falling back to old probe method for modesetting
  [13.135] (EE) open /dev/dri/card0: No such file or directory
  [13.135] (II) Loading sub module "fbdevhw"
  [13.135] (II) LoadModule: "fbdevhw"
  [13.136] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  [13.137] (II) Module fbdevhw: vendor="X.Org Foundation"
  [13.137]compiled for 1.19.6, module version = 0.0.2
  [13.137]ABI class: X.Org Video Driver, version 23.0
  [13.137] (**) FBDEV(2): claimed PCI slot 1@0:0:0
  [13.137] (II) FBDEV(2): using default device
  [13.137] (WW) Falling back to old probe method for vesa
  [13.137] (EE) Screen 0 deleted because of no matching config section.
  [13.137] (II) UnloadModule: "radeon"
  [13.137] (EE) Screen 0 deleted because of no matching config section.
  [13.137] (II) UnloadModule: "modesetting"
  [13.138] (II) FBDEV(0): Creating default Display subsection in Screen 
section
  "Default Screen Section" for depth/fbbpp 24/32
  [13.138] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32

  After some digging, on another computer, adding nomodeset to the
  kernal startup parameters helps. Edited /etc/default/grub

  GRUB_CMDLINE_LINUX="nomodeset"

  $update-grub
  provides a usable but degraded session. 

  The screen resolution is 1400x1050.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp


[Desktop-packages] [Bug 1803885] [NEW] Lenovo R60 screen corrupt immediately after install

2018-11-18 Thread CoderGuy
Public bug reported:

Version : Ubuntu 18.04.1 LTS

Immediately after the install completes. The computer restarts to a
corrupt login screen.

Hardware : Lenovo R60
Video : 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] RV515/M54 [Mobility Radeon X1400]

Xorg.log

AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
MULLINS, KAVERI, HAWAII
[13.133] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[13.133] (II) FBDEV: driver for framebuffer: fbdev
[13.133] (II) VESA: driver for VESA chipsets: vesa
[13.135] (II) [KMS] drm report modesetting isn't supported.
[13.135] (EE) open /dev/dri/card0: No such file or directory
[13.135] (WW) Falling back to old probe method for modesetting
[13.135] (EE) open /dev/dri/card0: No such file or directory
[13.135] (II) Loading sub module "fbdevhw"
[13.135] (II) LoadModule: "fbdevhw"
[13.136] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[13.137] (II) Module fbdevhw: vendor="X.Org Foundation"
[13.137]compiled for 1.19.6, module version = 0.0.2
[13.137]ABI class: X.Org Video Driver, version 23.0
[13.137] (**) FBDEV(2): claimed PCI slot 1@0:0:0
[13.137] (II) FBDEV(2): using default device
[13.137] (WW) Falling back to old probe method for vesa
[13.137] (EE) Screen 0 deleted because of no matching config section.
[13.137] (II) UnloadModule: "radeon"
[13.137] (EE) Screen 0 deleted because of no matching config section.
[13.137] (II) UnloadModule: "modesetting"
[13.138] (II) FBDEV(0): Creating default Display subsection in Screen 
section
"Default Screen Section" for depth/fbbpp 24/32
[13.138] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32

After some digging, on another computer, adding nomodeset to the kernal
startup parameters helps. Edited /etc/default/grub

GRUB_CMDLINE_LINUX="nomodeset"

$update-grub
provides a usable but degraded session. 

The screen resolution is 1400x1050.

** Affects: xserver-xorg-video-ati (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1803885

Title:
  Lenovo R60 screen corrupt immediately after install

Status in xserver-xorg-video-ati package in Ubuntu:
  New

Bug description:
  Version : Ubuntu 18.04.1 LTS

  Immediately after the install completes. The computer restarts to a
  corrupt login screen.

  Hardware : Lenovo R60
  Video : 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] RV515/M54 [Mobility Radeon X1400]

  Xorg.log

  AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series, BARTS,
  AMD Radeon HD 6800 Series, AMD Radeon HD 6700 Series, TURKS, CAICOS,
  ARUBA, TAHITI, PITCAIRN, VERDE, OLAND, HAINAN, BONAIRE, KABINI,
  MULLINS, KAVERI, HAWAII
  [13.133] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
  [13.133] (II) FBDEV: driver for framebuffer: fbdev
  [13.133] (II) VESA: driver for VESA chipsets: vesa
  [13.135] (II) [KMS] drm report modesetting isn't supported.
  [13.135] (EE) open /dev/dri/card0: No such file or directory
  [13.135] (WW) Falling back to old probe method for modesetting
  [13.135] (EE) open /dev/dri/card0: No such file or directory
  [13.135] (II) Loading sub module "fbdevhw"
  [13.135] (II) LoadModule: "fbdevhw"
  [13.136] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  [13.137] (II) Module fbdevhw: vendor="X.Org Foundation"
  [13.137]compiled for 1.19.6, module version = 0.0.2
  [13.137]ABI class: X.Org Video Driver, version 23.0
  [13.137] (**) FBDEV(2): claimed PCI slot 1@0:0:0
  [13.137] (II) FBDEV(2): using default device
  [13.137] (WW) Falling back to old probe method for vesa
  [13.137] (EE) Screen 0 deleted because of no matching config section.
  [13.137] (II) UnloadModule: "radeon"
  [13.137] (EE) Screen 0 deleted because of no matching config section.
  [13.137] (II) UnloadModule: "modesetting"
  [13.138] (II) FBDEV(0): Creating default Display subsection in Screen 
section
  "Default Screen Section" for depth/fbbpp 24/32
  [13.138] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32

  After some digging, on another computer, adding nomodeset to the
  kernal startup parameters helps. Edited /etc/default/grub

  GRUB_CMDLINE_LINUX="nomodeset"

  $update-grub
  provides a usable but degraded session. 

  The screen resolution is 1400x1050.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1803885/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-pa

[Desktop-packages] [Bug 841039] Re: Banshee does not detect iPod Touch

2011-09-15 Thread CoderGuy
I found the solution...

I had to remove the gnome-device-manager.  Once this was done I was able
to sync without a problem in Rhythmbox. Banshee could not see the
already present music, or detect the usage correctly though.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/841039

Title:
  Banshee does not detect iPod Touch

Status in “banshee” package in Ubuntu:
  New

Bug description:
  When I Start banshee and Connect the iPod. An Apple IPod is shown in
  the devices section. Clicking on music Shows no content. And I cannot
  sync any content.

  In nautilus I am able to browse the device without a problem.

  
  The following is shown in the terminal,

  NOTE: The ipod does not show up at all in Rhthymbox

  [Warn  15:53:03.562] Failed to load media-player-info file for 1

  ** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
  Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
  LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  [Warn  15:53:05.244] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
    at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0
    at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0
    at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0
  [Warn  15:53:05.748] Failed to load media-player-info file for 1
  [Warn  15:53:06.550] Failed to load media-player-info file for 1

  ** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
  Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
  LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  [Warn  15:53:08.575] Failed to load media-player-info file for 1
  [Warn  15:53:12.412] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
    at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0
    at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0
    at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0
  [Warn  15:53:12.742] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Bansh

[Desktop-packages] [Bug 841039] Re: Banshee does not detect iPod Touch

2011-09-15 Thread CoderGuy
Disconnected

alec@BigOne:~$ ls -al ~/.gvfs
total 16
drwx--   2 alec alec  4096 2011-09-15 22:37 .
drwx-- 133 alec alec 12288 2011-09-15 22:37 ..

Connected

alec@BigOne:~$ ls -al ~/.gvfs
total 16
drwx--   2 alec alec  4096 2011-09-15 22:37 .
drwx-- 133 alec alec 12288 2011-09-15 22:37 ..

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to banshee in Ubuntu.
https://bugs.launchpad.net/bugs/841039

Title:
  Banshee does not detect iPod Touch

Status in “banshee” package in Ubuntu:
  New

Bug description:
  When I Start banshee and Connect the iPod. An Apple IPod is shown in
  the devices section. Clicking on music Shows no content. And I cannot
  sync any content.

  In nautilus I am able to browse the device without a problem.

  
  The following is shown in the terminal,

  NOTE: The ipod does not show up at all in Rhthymbox

  [Warn  15:53:03.562] Failed to load media-player-info file for 1

  ** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
  Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
  LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  [Warn  15:53:05.244] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
    at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0
    at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0
    at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0
  [Warn  15:53:05.748] Failed to load media-player-info file for 1
  [Warn  15:53:06.550] Failed to load media-player-info file for 1

  ** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
  Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
  LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  [Warn  15:53:08.575] Failed to load media-player-info file for 1
  [Warn  15:53:12.412] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
    at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0
    at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0
    at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0
  [Warn  15:53:12.742] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
    at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
    at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullRef

[Desktop-packages] [Bug 841039] Re: Banshee does not detect iPod Touch

2011-09-04 Thread CoderGuy
** Description changed:

  When I Start banshee and Connect the iPod. An Apple IPod is shown in the
- devices section. Clicking on music Shows no content.
+ devices section. Clicking on music Shows no content. And I cannot sync
+ any content.
+ 
+ In nautilus I am able to browse the device without a problem.
+ 
  
  The following is shown in the terminal,
  
  NOTE: The ipod does not show up at all in Rhthymbox
  
  [Warn  15:53:03.562] Failed to load media-player-info file for 1
  
  ** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
  Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
  LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  [Warn  15:53:05.244] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
-   at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0 
-   at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0 
-   at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0 
+   at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0
+   at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0
+   at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0
  [Warn  15:53:05.748] Failed to load media-player-info file for 1
  [Warn  15:53:06.550] Failed to load media-player-info file for 1
  
  ** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
  Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
  LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  LIBMTP PANIC: could not inspect object property descriptions!
  [Warn  15:53:08.575] Failed to load media-player-info file for 1
  [Warn  15:53:12.412] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
-   at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0 
-   at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0 
-   at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0 
+   at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, 
System.UInt16& maxLevel, System.UInt16& currentLevel) [0x0] in :0
+   at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0
+   at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0
  [Warn  15:53:12.742] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
-   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
-   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0 
+   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
+   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
-   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
-   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0 
+   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
+   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
-   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
-   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0 
+   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
+   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
-   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
-   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0 
+   at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0
+   at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in 
:0
  [Warn  15:53:12.743] Caught

[Desktop-packages] [Bug 841039] Re: Banshee does not detect iPod Touch

2011-09-04 Thread CoderGuy
This happens in Natty. For completeness this is the output from
rhythmbox -d.

(16:06:52) [0x1c62040] [uevent_cb] rb-removable-media-manager.c:548: add event 
for /sys/devices/pci:00/:00:10.4/usb1/1-2 (bd06)
(16:06:52) [0x1c62040] [uevent_cb] rb-removable-media-manager.c:548: add event 
for /sys/devices/pci:00/:00:10.4/usb1/1-2/1-2:3.1 (0)
(16:06:52) [0x1c62040] [uevent_cb] rb-removable-media-manager.c:548: add event 
for /sys/devices/pci:00/:00:10.4/usb1/1-2/1-2:1.0 (0)
(16:06:52) [0x1c62040] [uevent_cb] rb-removable-media-manager.c:548: remove 
event for /sys/devices/pci:00/:00:10.4/usb1/1-2/1-2:1.0 (0)
(16:06:52) [0x1c62040] [uevent_cb] rb-removable-media-manager.c:548: add event 
for /sys/devices/pci:00/:00:10.4/usb1/1-2/1-2:3.0 (0)
(16:06:53) [0x1c62040] [dump_volume_identifiers] 
rb-removable-media-manager.c:621: uuid = 
7313296eb2919dc9ac6ecd98cb80d90cf974f166
(16:06:53) [0x1c62040] [rb_removable_media_manager_add_volume] 
rb-removable-media-manager.c:666: Unhandled media
(16:06:55) [0x1c62040] [dump_volume_identifiers] 
rb-removable-media-manager.c:621: uuid = 
7313296eb2919dc9ac6ecd98cb80d90cf974f166
(16:06:55) [0x1c62040] [rb_removable_media_manager_add_volume] 
rb-removable-media-manager.c:666: Unhandled media
(16:06:55) [0x1c62040] [rb_removable_media_manager_remove_volume] 
rb-removable-media-manager.c:679: volume removed
(16:06:55) [0x1c62040] [rb_removable_media_manager_remove_volume] 
rb-removable-media-manager.c:679: volume removed
(16:06:55) [0x1c62040] [rhythmdb_mount_added_cb] rhythmdb-monitor.c:430: volume 
afc://7313296eb2919dc9ac6ecd98cb80d90cf974f166/ mounted
(16:06:55) [0x1c62040] [rhythmdb_read_enter] rhythmdb.c:1239: counter: 1
(16:06:55) [0x1c62040] [rhythmdb_query_internal] rhythmdb.c:3997: doing query
(16:06:55) [0x1c62040] [do_query_recurse] rhythmdb-tree.c:2301: doing recursive 
query, 1 conjunctions
(16:06:55) [0x1c62040] [rhythmdb_query_internal] rhythmdb.c:4003: completed
(16:06:55) [0x1c62040] [rhythmdb_mount_added_cb] rhythmdb-monitor.c:444: 0 
mounted entries to process
(16:06:55) [0x1c62040] [rb_removable_media_manager_add_mount] 
rb-removable-media-manager.c:708: Unhandled media, no volume for mount
(16:06:55) [0x1c62040] [rhythmdb_process_one_event] rhythmdb.c:2538: processing 
RHYTHMDB_EVENT_QUERY_COMPLETE
(16:06:55) [0x1c62040] [rhythmdb_read_leave] rhythmdb.c:1253: counter: 0
(16:06:56) [0x1c62040] [dump_volume_identifiers] 
rb-removable-media-manager.c:621: uuid = 
7313296eb2919dc9ac6ecd98cb80d90cf974f166
(16:06:56) [0x1c62040] [rb_removable_media_manager_add_volume] 
rb-removable-media-manager.c:666: Unhandled media
(16:06:56) [0x1c62040] [rhythmdb_mount_added_cb] rhythmdb-monitor.c:430: volume 
afc://7313296eb2919dc9ac6ecd98cb80d90cf974f166/ mounted
(16:06:56) [0x1c62040] [rhythmdb_read_enter] rhythmdb.c:1239: counter: 1
(16:06:56) [0x1c62040] [rhythmdb_query_internal] rhythmdb.c:3997: doing query
(16:06:56) [0x1c62040] [do_query_recurse] rhythmdb-tree.c:2301: doing recursive 
query, 1 conjunctions
(16:06:56) [0x1c62040] [rhythmdb_query_internal] rhythmdb.c:4003: completed
(16:06:56) [0x1c62040] [rhythmdb_mount_added_cb] rhythmdb-monitor.c:444: 0 
mounted entries to process
(16:06:56) [0x1c62040] [dump_volume_identifiers] 
rb-removable-media-manager.c:621: uuid = 
7313296eb2919dc9ac6ecd98cb80d90cf974f166
no input path specified, can't find mount pointno input path specified, can't 
find device path
(16:06:56) [0x1c62040] [rb_plugin_find_file] rb-plugin.c:329: found 
'/usr/lib/rhythmbox/plugins/ipod/ipod-init.ui' when searching for file 
'ipod-init.ui' for plugin 'ipod'
(16:06:56) [0x1c62040] [rb_removable_media_manager_add_mount] 
rb-removable-media-manager.c:742: Unhandled media
(16:06:56) [0x1c62040] [rhythmdb_process_one_event] rhythmdb.c:2538: processing 
RHYTHMDB_EVENT_QUERY_COMPLETE
(16:06:56) [0x1c62040] [rhythmdb_read_leave] rhythmdb.c:1253: counter: 0
(16:06:57) [0x1c62040] [rhythmdb_mount_added_cb] rhythmdb-monitor.c:430: volume 
afc://7313296eb2919dc9ac6ecd98cb80d90cf974f166:3/ mounted
(16:06:57) [0x1c62040] [rhythmdb_read_enter] rhythmdb.c:1239: counter: 1
(16:06:57) [0x1c62040] [rhythmdb_query_internal] rhythmdb.c:3997: doing query
(16:06:57) [0x1c62040] [do_query_recurse] rhythmdb-tree.c:2301: doing recursive 
query, 1 conjunctions
(16:06:57) [0x1c62040] [rhythmdb_query_internal] rhythmdb.c:4003: completed
(16:06:57) [0x1c62040] [rhythmdb_mount_added_cb] rhythmdb-monitor.c:444: 0 
mounted entries to process
(16:06:57) [0x1c62040] [rb_removable_media_manager_add_mount] 
rb-removable-media-manager.c:708: Unhandled media, no volume for mount
(16:06:57) [0x1c62040] [rhythmdb_process_one_event] rhythmdb.c:2538: processing 
RHYTHMDB_EVENT_QUERY_COMPLETE
(16:06:57) [0x1c62040] [rhythmdb_read_leave] rhythmdb.c:1253: counter: 0
(16:06:57) [0x1c62040] [rb_uri_could_be_podcast] rb-file-helpers.c:601: 
'afc://7313296eb2919dc9ac6ecd98cb80d90cf974f166/' can't be a Podcast or OPML 
file, not the right scheme
(16:06:57) [0

[Desktop-packages] [Bug 841039] [NEW] Banshee does not detect iPod Touch

2011-09-04 Thread CoderGuy
Public bug reported:

When I Start banshee and Connect the iPod. An Apple IPod is shown in the
devices section. Clicking on music Shows no content.

The following is shown in the terminal,

NOTE: The ipod does not show up at all in Rhthymbox

[Warn  15:53:03.562] Failed to load media-player-info file for 1

** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
LIBMTP PANIC: could not inspect object property descriptions!
LIBMTP PANIC: could not inspect object property descriptions!
[Warn  15:53:05.244] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
  at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, System.UInt16& 
maxLevel, System.UInt16& currentLevel) [0x0] in :0 
  at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0 
  at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0 
[Warn  15:53:05.748] Failed to load media-player-info file for 1
[Warn  15:53:06.550] Failed to load media-player-info file for 1

** (Banshee:2080): CRITICAL **: itdb_get_control_dir: assertion `mountpoint' 
failed
Device 0 (VID=05ac and PID=1293) is a Apple iPod Touch 2nd Gen.
LIBMTP WARNING: no MTP vendor extension on device 5 on bus 1LIBMTP WARNING: 
VendorExtensionID: LIBMTP WARNING: VendorExtensionDesc: Device has no 
vendor extensionsLIBMTP WARNING: this typically means the device is PTP (i.e. a 
camera) but not an MTP device at all. Trying to continue anyway.LIBMTP PANIC: 
could not inspect object property descriptions!
LIBMTP PANIC: could not inspect object property descriptions!
LIBMTP PANIC: could not inspect object property descriptions!
[Warn  15:53:08.575] Failed to load media-player-info file for 1
[Warn  15:53:12.412] Unable to get battery level from MTP device - 
Mtp.LibMtpException: Could not retrieve battery stats (in `Mtp')
  at Mtp.MtpDevice.GetBatteryLevel (Mtp.MtpDeviceHandle handle, System.UInt16& 
maxLevel, System.UInt16& currentLevel) [0x0] in :0 
  at Mtp.MtpDevice.get_BatteryLevel () [0x0] in :0 
  at Banshee.Dap.Mtp.MtpSource.DeviceInitialize (IDevice device) [0x0] in 
:0 
[Warn  15:53:12.742] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0] in :0 
[Warn  15:53:12.743] Caught an exception - System.NullReferenceException: 
Object reference not set to an instance of an object (in `Banshee.Dap')
  at Banshee.Dap.Gui.DapInfoBar.UpdateUsage () [0x0] in :0 
  at Banshee.Dap.Gui.DapInfoBar.m__4 () [0x0]