[Bug 1821012] Re: can t run snap gnome-system-monitor

[HankB]

The snap is now working. (In other words, not able to reproduce.)
I'm not sure what made the change but I did reboot several times.

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

Title:
  can t run snap gnome-system-monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1821012/+subscriptions

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

[Bug 1821012] [NEW] can t run snap gnome-system-monitor

[HankB]

Public bug reported:

Can't run from 'gnome find' - nothing happens.
Try to run from terminal - get this:

hbarta@karakum:~$ gnome-system-monitor 
You need to connect this snap to the gnome platform snap.

You can do this with those commands:
snap install gnome-3-26-1604
snap connect gnome-system-monitor:gnome-3-26-1604 gnome-3-26-1604

(the '3-26-1604' number defines the platform version and might change)
hbarta@karakum:~$ 
hbarta@karakum:~$ snap install gnome-3-26-1604
snap "gnome-3-26-1604" is already installed, see 'snap help refresh'
hbarta@karakum:~$ snap connect gnome-system-monitor:gnome-3-26-1604 
gnome-3-26-1604
error: snap "gnome-system-monitor" has no plug named "gnome-3-26-1604"
hbarta@karakum:~$ 

Remove snap, install deb - runs OK.

Remove deb, install snap (with intent to see if this fixes the issue or
to file a bug report) and now get

hbarta@karakum:~$ gnome-system-monitor
Failed to register: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An 
AppArmor policy prevents this sender from sending this message to this 
recipient; type="method_call", sender=":1.112" (uid=1000 pid=10105 
comm="gnome-system-monitor " 
label="snap.gnome-system-monitor.gnome-system-monitor (enforce)") 
interface="org.gtk.Actions" member="DescribeAll" error name="(unset)" 
requested_reply="0" destination="org.gnome.SystemMonitor" (uid=1000 pid=3975 
comm="gnome-system-monitor " label="unconfined")
hbarta@karakum:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-system-monitor (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 20 09:05:16 2019
InstallationDate: Installed on 2019-01-30 (48 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-system-monitor
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-system-monitor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  can t run snap gnome-system-monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1821012/+subscriptions

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

[Bug 1808398] Re: top right menu does not display when activated

[HankB]

Additional information that might matter... I have a second monitor
connected via HDMI output. Monitor is 1600x1200 and is rotated 90
degrees. It had problems on 18.04 with Wayland
(https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226) and
I have attached the output of xrandr when run from Xorg.

This does matter. I rebooted with the second monitor not connected and
the problem with the menu does not occur.

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+attachment/5222187/+files/xrandr.txt

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

Title:
  top right menu does not display when activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+subscriptions

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

[Bug 1808398] Re: top right menu does not display when activated

[HankB]

first requested file

** Attachment added: "lspci -k"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+attachment/5222182/+files/pci.txt

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

Title:
  top right menu does not display when activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+subscriptions

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

[Bug 1808398] Re: top right menu does not display when activated

[HankB]

second requested file

This is a Lenovo Y50 which also has an Nvidia 860m (IIRC) which does not
appear in the list of PCI devices so I must have disabled it in the BIOS
or it is no longer working.

Thank you for your help.

** Attachment added: "dpkg -l"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+attachment/5222185/+files/allpackages.txt

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

Title:
  top right menu does not display when activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+subscriptions

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

[Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist

[HankB]

It looks like your comment is appropriate:
86204" TYPE="zfs_member" PTUUID="eba09d2e-0f70-4d11-8e37-c1c170cfd9dd"
PTTYPE="gpt"

Is the correct response to "follow up with the authors of the util-linux
package?"

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

Title:
  gparted produces unusual results when ZFS partitios exist

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

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

[Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist

[HankB]

That gitlab issue looks like what I'm seeing. I've collected the requested 
information. Can you confirm this is the problem?
hbarta@saugage:~$ sudo blkid /dev/sda
[sudo] password for hbarta: 
/dev/sda: LABEL="rpool" UUID="4510611204828545482" 
UUID_SUB="9816084798696086204" TYPE="zfs_member" 
PTUUID="eba09d2e-0f70-4d11-8e37-c1c170cfd9dd" PTTYPE="gpt"
hbarta@saugage:~$ sudo wipefs --no-act /dev/sda
DEVICE OFFSET   TYPE   UUIDLABEL
sda0xe8e0d3f000 zfs_member 4510611204828545482 rpool
sda0xe8e0d3e000 zfs_member 4510611204828545482 rpool
sda0xe8e0d3d000 zfs_member 4510611204828545482 rpool
sda0xe8e0d3c000 zfs_member 4510611204828545482 rpool
sda0xe8e0d3b000 zfs_member 4510611204828545482 rpool
sda0xe8e0d3a000 zfs_member 4510611204828545482 rpool
sda0xe8e0d39000 zfs_member 4510611204828545482 rpool
sda0xe8e0d38000 zfs_member 4510611204828545482 rpool
sda0xe8e0d37000 zfs_member 4510611204828545482 rpool
sda0xe8e0d36000 zfs_member 4510611204828545482 rpool
sda0xe8e0d35000 zfs_member 4510611204828545482 rpool
sda0xe8e0d34000 zfs_member 4510611204828545482 rpool
sda0xe8e0d33000 zfs_member 4510611204828545482 rpool
sda0xe8e0d32000 zfs_member 4510611204828545482 rpool
sda0xe8e0d31000 zfs_member 4510611204828545482 rpool
sda0xe8e0d3 zfs_member 4510611204828545482 rpool
sda0xe8e0d2f000 zfs_member 4510611204828545482 rpool
sda0xe8e0d2e000 zfs_member 4510611204828545482 rpool
sda0xe8e0d2d000 zfs_member 4510611204828545482 rpool
sda0xe8e0d2c000 zfs_member 4510611204828545482 rpool
sda0xe8e0d2b000 zfs_member 4510611204828545482 rpool
sda0xe8e0d2a000 zfs_member 4510611204828545482 rpool
sda0xe8e0d29000 zfs_member 4510611204828545482 rpool
sda0xe8e0d28000 zfs_member 4510611204828545482 rpool
sda0xe8e0d27000 zfs_member 4510611204828545482 rpool
sda0xe8e0d26000 zfs_member 4510611204828545482 rpool
sda0xe8e0d25000 zfs_member 4510611204828545482 rpool
sda0xe8e0d24000 zfs_member 4510611204828545482 rpool
sda0xe8e0d23000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7f000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7e000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7d000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7c000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7b000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7a000 zfs_member 4510611204828545482 rpool
sda0xe8e0d79000 zfs_member 4510611204828545482 rpool
sda0xe8e0d78000 zfs_member 4510611204828545482 rpool
sda0xe8e0d77000 zfs_member 4510611204828545482 rpool
sda0xe8e0d76000 zfs_member 4510611204828545482 rpool
sda0xe8e0d75000 zfs_member 4510611204828545482 rpool
sda0xe8e0d74000 zfs_member 4510611204828545482 rpool
sda0xe8e0d73000 zfs_member 4510611204828545482 rpool
sda0xe8e0d72000 zfs_member 4510611204828545482 rpool
sda0xe8e0d71000 zfs_member 4510611204828545482 rpool
sda0xe8e0d7 zfs_member 4510611204828545482 rpool
sda0xe8e0d6f000 zfs_member 4510611204828545482 rpool
sda0xe8e0d6e000 zfs_member 4510611204828545482 rpool
sda0xe8e0d6d000 zfs_member 4510611204828545482 rpool
sda0xe8e0d6c000 zfs_member 4510611204828545482 rpool
sda0xe8e0d6b000 zfs_member 4510611204828545482 rpool
sda0xe8e0d6a000 zfs_member 4510611204828545482 rpool
sda0xe8e0d69000 zfs_member 4510611204828545482 rpool
sda0xe8e0d68000 zfs_member 4510611204828545482 rpool
sda0xe8e0d67000 zfs_member 4510611204828545482 rpool
sda0xe8e0d66000 zfs_member 4510611204828545482 rpool
sda0xe8e0d65000 zfs_member 4510611204828545482 rpool
sda0xe8e0d64000 zfs_member 4510611204828545482 rpool
sda0xe8e0d63000 zfs_member 4510611204828545482 rpool
sda0xe8e0d62000 zfs_member 4510611204828545482 rpool
sda0xe8e0d61000 zfs_member 4510611204828545482 rpool
sda0xe8e0d6 zfs_member 4510611204828545482 rpool
sda0x200gpt
sda0xe8e0db5e00 gpt
sda0x1fePMBR   
hbarta@saugage:~$

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

Title:
  gparted produces unusual results when ZFS partitios exist

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

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

[Bug 1808421] [NEW] gparted produces unusual results when ZFS partitios exist

[HankB]

Public bug reported:

Run gparted on a disk that has ZFS partitions. It shows one entire
partition. Parted seems to display correctly. gparted image attached.

hbarta@saugage:~$ sudo parted /dev/sda
GNU Parted 3.2
Using /dev/sda
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p
Model: ATA Samsung SSD 850 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   EndSizeFile system  Name  Flags
 1  1049kB  538MB  537MB   fat32  boot, 
esp
 2  538MB   555MB  16.8MB  zfs  Microsoft reserved partition  
msftres
 3  555MB   105GB  105GB   ntfs Basic data partition  
msftdata
 4  105GB   420GB  315GB   zfs  rpool

(parted) q
hbarta@saugage:~$ 

hbarta@saugage:~$ sudo sgdisk -p /dev/sda
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Model: Samsung SSD 850 
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): EBA09D2E-0F70-4D11-8E37-C1C170CFD9DD
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 1133243757 sectors (540.4 GiB)

Number  Start (sector)End (sector)  Size   Code  Name
   12048 1050623   512.0 MiB   EF00  
   2 1050624 1083391   16.0 MiB0C01  Microsoft reserved ...
   3 1083392   205883391   97.7 GiB0700  Basic data partition
   4   205883392   820283391   293.0 GiB   8300  rpool
hbarta@saugage:~$

hbarta@saugage:~$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10
hbarta@saugage:~$ 

Reproduce: 
1) Configure (perhaps install) Ubuntu on a drive with a ZFS partition.
2) Open gparted.

Note: Same issue happens with gparted on the 18.04.1 desktop install
USB.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gparted 0.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 13 15:05:13 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: gparted
UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

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


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  gparted produces unusual results when ZFS partitios exist

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

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

[Bug 1808421] Re: gparted produces unusual results when ZFS partitios exist

[HankB]

Problem gparted display.

** Attachment added: "Screenshot from 2018-12-13 15-03-21-crop.png"
   
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1808421/+attachment/5222132/+files/Screenshot%20from%202018-12-13%2015-03-21-crop.png

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

Title:
  gparted produces unusual results when ZFS partitios exist

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

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

[Bug 1808398] [NEW] top right menu does not display when activated

[HankB]

Public bug reported:

1) Install Ubuntu 18.04.1 via debbootstrap
2) Install ubuntu-desktop package
3) Install vanilla-desktop package
4) Upgrade to 18.10 using the Software GUI
5) Log into Ubuntu on Wayland
6) Click right end of top bar, menu drops down.
7) Mouse over menu, no visual feedback of focus (as with Ubuntu on Xorg)
8) Interact with menu items - there is no visual feedback. For example 
 - sliding back and forth on the screen brightness slider causes the screen 
brightness to change as expected but the slider does not reflect changes. 
Clicking on the right end of the top bar causes the menu to deactivate but 
before it does, the slider position updates.
 - click on the user name and nothing appears to happen. Click below it where 
the submenu would appear causes the submenu to activate. (the logout dialog 
appears.)

I'm not sure if steps 1-4 are required vs. just installing 18.10 but I
list it in case this results from left over settings from 18.04
installing via debbootstrap.

hbarta@saugage:~$ lsb_release -rd
Description:Ubuntu 18.10
Release:18.10
hbarta@saugage:~$ 

hbarta@saugage:~$ apt-cache policy gnome-shell mutter xwayland gnome-menus 
libgnome-menu-3-0:amd64
gnome-shell:
  Installed: 3.30.1-2ubuntu1.18.10.1
  Candidate: 3.30.1-2ubuntu1.18.10.1
  Version table:
 *** 3.30.1-2ubuntu1.18.10.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.30.1-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
mutter:
  Installed: 3.30.2-1~ubuntu18.10.1
  Candidate: 3.30.2-1~ubuntu18.10.1
  Version table:
 *** 3.30.2-1~ubuntu18.10.1 500
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 3.30.1-1 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
xwayland:
  Installed: 2:1.20.1-3ubuntu2.1
  Candidate: 2:1.20.1-3ubuntu2.1
  Version table:
 *** 2:1.20.1-3ubuntu2.1 500
500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 
Packages
500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages
100 /var/lib/dpkg/status
 2:1.20.1-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
gnome-menus:
  Installed: 3.13.3-11ubuntu2
  Candidate: 3.13.3-11ubuntu2
  Version table:
 *** 3.13.3-11ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
libgnome-menu-3-0:
  Installed: 3.13.3-11ubuntu2
  Candidate: 3.13.3-11ubuntu2
  Version table:
 *** 3.13.3-11ubuntu2 500
500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
hbarta@saugage:~$ 


Expected behavior: menu provides visual feedback to clicks. Underlying action 
seems to happen but there is no hint of that or display of submenus.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 13 11:41:23 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to cosmic on 2018-12-13 (0 days ago)
mtime.conffile..etc.logrotate.d.apport: 2018-12-12T13:31:49.347693

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  top right menu does not display when activated

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808398/+subscriptions

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

[Bug 1808226] Re: Rotated screen is blank in Wayland sessions [Failed to set CRTC mode 1600x1200: No space left on device]

[HankB]

I updated to 18.10 in place. That fixes the problem with the blank
screen. Unfortunately the menu to the upper left does not seem to get
focus. To logout I go to the upper right and type logout which loads a
'logout app.' I suppose that's a different bug.

Thank you for your help. Please let me know if you would like further
testing. I'm working with scripts to install Ubuntu (and Debian) on ZFS
root and can load up a fresh install in a little longer than it takes to
install using the conventional installer.

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

Title:
  Rotated screen is blank in Wayland sessions [Failed to set CRTC mode
  1600x1200: No space left on device]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions

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

[Bug 1808226] Re: rotated screen is blank

[HankB]

Yes, seems to be related to Wayland.

I have attached xrandr output from an Xorg session.

Thanks!

** Attachment added: "xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+attachment/5221818/+files/xrandr.txt

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

Title:
  rotated screen is blank

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions

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

[Bug 1808226] [NEW] rotated screen is blank

[HankB]

Public bug reported:

Using "ubuntu-gnome-desktop"  ("vanilla-gnome-desktop" also installed)
with external 1600x1200 monitor rotated 90 deg. Monitor connected via
HDMI and using Inel i915 driver.

1) Login to "Ubuntu" session. Use Settings -> Display to rotate monitor 90 deg 
left. Accept new settings. Logout.
2) Login to "Ubuntu on Wayland" External monitor gets no signal. 
Following line at the end of 'dmesg' output seems to relate to the issue:
Dec 12 14:37:46 saugage gnome-shell[6125]: Failed to set CRTC mode 1600x1200: 
No space left on device

Searching for this message reveals several reports of Gnome Shell
crashing at this point. It does not crash for me but the external
monitor remains unusable.

hbarta@saugage:/var/log$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
hbarta@saugage:/var/log$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.3
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:44:42 2018
DisplayManager: gdm3
GsettingsChanges:
 b'org.gnome.shell' b'command-history' redacted by apport
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic wayland-session

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

Title:
  rotated screen is blank

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1808226/+subscriptions

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

[Bug 1808220] [NEW] dpkg-reconfigure locales does not add locale to /etc/default/locale

[HankB]

Public bug reported:

1) Install Ubuntu 18.04 via debbootstrap (following instructions at 
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS)
2) install ubuntu-desktop (`apt install ubuntu0desktop`)
3) reboot.
Content of /etc/default/locale is one line "LANG=en_US"
Consequence of this is that an xterm will not start resulting in following 
errors in /var/log/syslog
Dec 12 13:37:52 saugage gnome-shell[12845]: Received error from DBus search 
provider org.gnome.Terminal.desktop: Gio.IOErrorEnum: Timeout was reached
Dec 12 13:37:57 saugage gnome-terminal.desktop[14431]: # Error constructing 
proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling 
StartServiceByName for org.gnome.Terminal: Timeout was reached

Tracking down the cause of the error indicated missing entry in 
/etc/default/locale. Adding the following solved problem:
  hbarta@saugage:~$ cat /etc/default/locale
  #  File generated by update-locale
  LANG=en_US
  LC_ALL="en_US.UTF-8"

hbarta@saugage:/var/log$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

When I ran `dpkg-reconfigure locales` I selected en_US for the default
locale.

Possibly related to bug #1598326

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: locales 2.27-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 12 14:06:53 2018
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US
 SHELL=/bin/bash
SourcePackage: glibc
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

  1) Install Ubuntu 18.04 via debbootstrap (following instructions at 
https://github.com/zfsonlinux/zfs/wiki/Ubuntu-18.04-Root-on-ZFS)
  2) install ubuntu-desktop (`apt install ubuntu0desktop`)
  3) reboot.
  Content of /etc/default/locale is one line "LANG=en_US"
  Consequence of this is that an xterm will not start resulting in following 
errors in /var/log/syslog
  Dec 12 13:37:52 saugage gnome-shell[12845]: Received error from DBus search 
provider org.gnome.Terminal.desktop: Gio.IOErrorEnum: Timeout was reached
  Dec 12 13:37:57 saugage gnome-terminal.desktop[14431]: # Error constructing 
proxy for org.gnome.Terminal:/org/gnome/Terminal/Factory0: Error calling 
StartServiceByName for org.gnome.Terminal: Timeout was reached
  
  Tracking down the cause of the error indicated missing entry in 
/etc/default/locale. Adding the following solved problem:
-   hbarta@saugage:~$ cat /etc/default/locale 
-   #  File generated by update-locale
-   LANG=en_US
-   LC_ALL="en_US.UTF-8"
+   hbarta@saugage:~$ cat /etc/default/locale
+   #  File generated by update-locale
+   LANG=en_US
+   LC_ALL="en_US.UTF-8"
  
  hbarta@saugage:/var/log$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
+ 
+ When I ran `dpkg-reconfigure locales` I selected en_US for the default
+ locale.
  
  Possibly related to bug #1598326
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: locales 2.27-3ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 12 14:06:53 2018
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US
+  SHELL=/bin/bash
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  dpkg-reconfigure locales does not add locale to /etc/default/locale

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

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

[Bug 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when running Skype or Slack snaps]

[HankB]

I'm seeing what I believe to be the same issue with Visual Studio Code.
If I try to start it after logging in using Gnome on Wayland, I find
myself looking at a login screen. (If I login to Gnome on Xorg this does
not happen.)

There is a core file in my home directory


There is also a file in /var/crashes
hbarta@karakum:~$ ls /var/crash
_usr_bin_pulseaudio.1000.crash  _usr_bin_Xwayland.1000.crash
hbarta@karakum:~$ 

hbarta@karakum:~$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 
-d', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, 
execfn: '/usr/bin/Xwayland', platform: 'x86_64'
hbarta@karakum:~$ 

I tried to install debug symbols for Xwayland but cannot.

hbarta@karakum:~$ sudo apt install xwayland-dbgsym
[sudo] password for hbarta: 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 xwayland-dbgsym : Depends: xwayland (= 2:1.19.6-1ubuntu4.1) but 
2:1.19.6-1ubuntu4 is to be installed
E: Unable to correct problems, you have held broken packages.
hbarta@karakum:~$ 

I have the same problem on Debian Testing but not Fedora 28. (On Debian
testing I am not running vs code as a snap.)

I would like to use Wayland for the improved monitor scaling so I can
use a 1600x1200 eternal monitor with a QHD laptop.

If there is any further information I could provide (and I'm sure I'm
light in this regard) please let me know.

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

Title:
  Xwayland crashed with SIGABRT in st_renderbuffer_delete() [often when
  running Skype or Slack snaps]

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

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

[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[HankB]

I have applied the fix (alternate kernel) and that did fix the problem.
However the alternate kernel is not without issues. I am unable to
install 'zfsutils-linux' because the zfs modules cannot be built. There
is more information at https://askubuntu.com/questions/1012083/cant-add-
zfs-to-17-10 and I can copy any relevant information here if
appropriate.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[HankB]

The kernel update worked for my Lenovo Y50-70 and I can now boot from
USB.

Thanks all for those who helped to fix this.

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

[Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

[HankB]

Now I understand why I can no longer boot any USB drive. >:(

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

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

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

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

Re: [Bug 1721317] Re: graphical installer crashed.

[HankB]

I have handed this off to another user and no longer have access to it.

On Thu, Nov 30, 2017 at 12:24 PM, Phillip Susi  wrote:

> Can you run sudo grub-probe /boot/efi?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721317
>
> Title:
>   graphical installer crashed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/
> +bug/1721317/+subscriptions
>


-- 
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois

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

Title:
  graphical installer crashed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1721317/+subscriptions

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

Re: [Bug 1721317] Re: graphical installer crashed.

[HankB]

I needed to get the install done so I went ahead and did a more normal
install with '/boot/efi' in an normal partition on the first disk. After
the install, I created a matching partition on the second drive, copied the
/boot/efi partition to that and then created a (degraded RAID) on the first
drive. (At this point I had destroyed /dev/md0 and recreated it.) I then
copied the data back to the RAID partition on the first drive, unmounted
the partition on the second and added it to complete the RAID1. The
partition was created as /dev/md0 (using 0.90 metadata) and after reboot
came up as /dev/md127. Other than that, it seems to work. Surprisingly the
block ID for /dev/md127 and the original EXT4 /boot/efi matched. But this
is all after the crash that triggered the bug report.

The command used to create the RAID device would have used the same
parameters as

root@androidlx01:~# mdadm --create /dev/md0 --metadata=0.90 -l raid1 -f -n
1 /dev/sda1

mdadm: /dev/sda1 appears to be part of a raid array:

  level=raid0 devices=0 ctime=Wed Dec 31 19:00:00 1969

Continue creating array? y

mdadm: array /dev/md0 started.

root@androidlx01:~# cat /proc/mdstat

Personalities : [raid1]

md0 : active raid1 sda1[0]

 524224 blocks [1/1] [U]


unused devices: 

The existing RAID is

androidadmin@androidlx01:~$ sudo mdadm -D /dev/md127
/dev/md127:
Version : 0.90
  Creation Time : Tue Oct 31 15:55:49 2017
 Raid Level : raid1
 Array Size : 524224 (512.02 MiB 536.81 MB)
  Used Dev Size : 524224 (512.02 MiB 536.81 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 127
Persistence : Superblock is persistent

Update Time : Fri Nov 10 15:33:49 2017
  State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

   UUID : 498041b2:09e636ad:d8fca355:d4d345d0 (local to host
androidlx01)
 Events : 0.40

Number   Major   Minor   RaidDevice State
   0   810  active sync   /dev/sda1
   1   8   171  active sync   /dev/sdb1
androidadmin@androidlx01:~$


On Tue, Oct 17, 2017 at 8:36 AM, Phillip Susi  wrote:

> Can you post the output of mdadm -D /dev/md0?
>
>
> ** Changed in: grub-installer (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1721317
>
> Title:
>   graphical installer crashed.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/
> +bug/1721317/+subscriptions
>


-- 
'03 BMW F650CS - hers
'98 Dakar K12RS - "BABY K" grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - "OUR LC"
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois

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

Title:
  graphical installer crashed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1721317/+subscriptions

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

[Bug 1721317] Re: graphical installer crashed.

[HankB]

Without rebooting I followed directions at
https://askubuntu.com/questions/83037/how-do-i-reinstall-grub2, mounted
/ and /boot/efi:

root@ubuntu:~# df
Filesystem 1K-blocksUsed Available Use% Mounted on
udev16421252   0  16421252   0% /dev
tmpfs32874609792   3277668   1% /run
/dev/sdc 1550400 1550400 0 100% /cdrom
/dev/loop0   1496320 1496320 0 100% /rofs
aufs16437292 2260244  14177048  14% /
tmpfs   16437292   18012  16419280   1% /dev/shm
tmpfs   5120   4  5116   1% /run/lock
tmpfs   16437292   0  16437292   0% /sys/fs/cgroup
tmpfs   16437292 524  16436768   1% /tmp
tmpfs3287460  84   3287376   1% /run/user/999
/dev/sdb2   50264772   53072  47635316   1% /mnt
/dev/md0  5232483496519752   1% /mnt/boot/efi
root@ubuntu:~# ls /mnt/boot/efi
EFI
root@ubuntu:~# ls /mnt/boot/efi/EFI/
Dell  ubuntu
root@ubuntu:~# grub-install --root-directory=/mnt /dev/sdb
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed 
in this setup by using blocklists.  However, blocklists are UNRELIABLE and 
their use is discouraged..
grub-install: error: will not proceed with blocklists.
root@ubuntu:~# grub-install --force --root-directory=/mnt /dev/sdb
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot 
Partition; embedding won't be possible.
grub-install: warning: Embedding is not possible.  GRUB can only be installed 
in this setup by using blocklists.  However, blocklists are UNRELIABLE and 
their use is discouraged..
Installation finished. No error reported.
root@ubuntu:~# update-grub
/usr/sbin/grub-probe: error: failed to get canonical path of `aufs'.
root@ubuntu:~# 

Tried to boot from BIOS (UEFI boot manager) selecting "integrated RAID
Controller 1: ubuntu" and got a "GRUB>" prompt. Seems like no way to
boot from second drive via the UEFI BIOS. Swapped drives with same
result.

or similar hoping

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

Title:
  graphical installer crashed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1721317/+subscriptions

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

[Bug 1721317] [NEW] graphical installer crashed.

[HankB]

Public bug reported:

Installing to /dev/sdb with /boot/efi on an MD RAID1 partition. Booted
to live environment, apt upgrade/update, install mdadm (and gparted)
brought up the RAID and started the install. Selected /dev/md0 for EFI
partition and /dev/sdb2 for '/' (formatted as EXT4) Selected /dev/sdb
for GRUB installation.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Wed Oct  4 12:52:56 2017
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial

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

Title:
  graphical installer crashed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1721317/+subscriptions

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

[Bug 660061] Re: Newer USB Startup Disks unbootable when created using Karmic 9.10

[HankB]

I'm encountering what looks like the same problem trying to install
ubuntu-10.04.2-desktop-i386.iso from a USB drive created using the
System - Administration - Startup Disk Creator (on a 10.10 host.)

I first get the Unknown keyword in configuration file: gfxboot
and then repeated:
===
vesamenu.c32: not a CPOM32R image
boot:
===
(This stuff between == repeated ad nauseum every 5 seconds.

Incidentally, both links above to possible solutions are 404.

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

Title:
  Newer USB Startup Disks unbootable when created using Karmic 9.10

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

[Bug 630748] Re: iwlagn degrades quickly during normal wifi session

[HankB]

I'm thoroughly confused. Yesterday I enabled N on my WAP and the
previously rock solid wireless connection for my Intel 5300 equipped
T500 became very unstable. Several times the connection dropped to the
point where network-manager presented me with the password page. At
other times it would drop and recover in a few seconds without
intervention. I found this bug report while trying to resolve the
problem. My T500 is still running 10.04.

I added the file /etc/modprobe.d/intel-5300-iwlagn-disable11n.conf with 
contents 
[code]options iwlagn 11n_disable=1[/code]
 and executed:
[code]sudo rmmod -f iwlagn
sudo modprobe iwlagn[/code]
and the card is still using N. Next I tried:
[code]sudo rmmod -f iwlagn
sudo modprobe iwlagn 11n_disable=1[/code]
Still running N and still unstable, though it did settle down and remained 
connected (or at least did not give up and ask for the password) overnight.

I have found information scattered throughout forum posts but have not
seen any that seem to have better info than what's in this bug report
and that seems less than complete. Questions I have:

Is 10.04 subject to the Intel firmware problem (or should I be looking
elsewhere for a solution to my problem.)

Is the syntax I'm using to disable N correct? Is that option not
supported by the module in 10.04?

Is there there better information on this bug?

thanks,
hank

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

Title:
  iwlagn degrades quickly during normal wifi session

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

Re: [Bug 626914] Re: upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead

[HankB]

So... If there's a bug and no one looks at it, it just goes away?

Fabulous.

Anyway, it's academic for me. I could not tolerate going to a beta
when I wanted to move to the next LTS so I did a clean onstall of
10.04.

thanks,
hank

On Wed, Dec 15, 2010 at 10:18 PM, Launchpad Bug Tracker
626...@bugs.launchpad.net wrote:
 [Expired for update-manager (Ubuntu) because there has been no activity
 for 60 days.]

 ** Changed in: update-manager (Ubuntu)
       Status: Incomplete = Expired

 --
 You received this bug notification because you are a direct subscriber
 of the bug.
 https://bugs.launchpad.net/bugs/626914

 Title:
  upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead


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

Title:
  upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead

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

[Bug 626914] Re: upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead

[HankB]

The attached tar file includes all files in /var/log/dist-upgrade

** Attachment added: all files in /var/log/dist-upgrade
   
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/626914/+attachment/1534359/+files/dist-upgrade.tgz

-- 
upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead
https://bugs.launchpad.net/bugs/626914
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 626914] [NEW] upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead

[HankB]

Public bug reported:

Binary package hint: update-manager

I followed directions to upgrade my 8.04 LTS server install to 10.04 LTS
on http://www.ubuntu.com/desktop/get-ubuntu/upgrade under Network
upgrade for Ubuntu servers (Recommended) Upon completion, the system
identifies itself as Maverick. I put a bit more detail in a post
http://ubuntuforums.org/showthread.php?p=9784929#post9784929

The bug report includes information from the system post upgrade.

I'm not sure if the bug is in the upgrade package or the way the
maverick betas are identified in the repos. It seems to me that the
upgrade package improperly identified the Maverick repos as the next LTS
candidage.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: update-manager-core 1:0.142.11
ProcVersionSignature: Ubuntu 2.6.35-19.28-server 2.6.35.3
Uname: Linux 2.6.35-19-server x86_64
Architecture: amd64
Date: Mon Aug 30 11:00:09 2010
ProcEnviron:
 LANGUAGE=en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: update-manager

** Affects: update-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug maverick

-- 
upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead
https://bugs.launchpad.net/bugs/626914
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 626914] Re: upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead

[HankB]

** Attachment added: Dependencies.txt
   
https://bugs.launchpad.net/bugs/626914/+attachment/1529708/+files/Dependencies.txt

-- 
upgrade from 8.04 LTS to 10.04 LTS installs Maverick instead
https://bugs.launchpad.net/bugs/626914
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 544506] Re: nautilus-sendto crashed with SIGSEGV in g_slice_alloc()

[HankB]

I have found that nautilus-sendto is crashing on my PC. Looking at 'dmesg' 
output shows the following results from three tries:
pre
[40839.267115] nautilus-sendto[4554]: segfault at  ip 
7fc6f65c12b4 sp 7fffcde1fd30 error 4 in 
libglib-2.0.so.0.2200.3[7fc6f6568000+c5000]
[40870.809221] nautilus-sendto[4560]: segfault at 10 ip 7fa8a439bf68 sp 
7fffd67f3c28 error 4 in libpango-1.0.so.0.2600.0[7fa8a4386000+46000]
[40885.457686] nautilus-sendto[4566]: segfault at  ip 
7fd51b69c2b4 sp 7fff9a338120 error 4 in 
libglib-2.0.so.0.2200.3[7fd51b643000+c5000]
/pre

Does this look like the same problem or should I file another bug
report?

thanks,
hank

-- 
nautilus-sendto crashed with SIGSEGV in g_slice_alloc()
https://bugs.launchpad.net/bugs/544506
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 413345] Re: incorrectly assumes /dev/mapper/ - LVM

[HankB]

I think I have experienced another facet of this bug. I had Jaunty
installed in /dev/sda with a separate /boot partition. When I installed
Karmic on another partition (also on /dev/sda) and *not* using the /boot
partition for Karmic, the resulting grub.cfg created entries for Jaunty
that ignored the separate /boot partition. In other words, In other
words, it produced:

menuentry Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sda6) {
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 7f69072f-cea2-4ec3-bde9-81dd16744034
linux /boot/vmlinuz-2.6.28-15-generic 
root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
initrd /boot/initrd.img-2.6.28-15-generic
}


when it should have been:

menuentry Ubuntu 9.04, kernel 2.6.28-15-generic (on /dev/sda6) {
insmod ext2
set root=(hd0,6)
search --no-floppy --fs-uuid --set 9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2
linux /vmlinuz-2.6.28-15-generic 
root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
initrd /initrd.img-2.6.28-15-generic
}

Annotated results from 'blkid'

r...@cypress:/media/disk/boot/grub# blkid
/dev/sda1: UUID=5C0CDB8F0CDB6296 LABEL=SERVICEV003 TYPE=ntfs 
/dev/sda2: UUID=C4F8DDE6F8DDD730 LABEL=SW_Preload TYPE=ntfs 
/dev/sda3: UUID=DE62E0C562E0A38D LABEL=Lenovo TYPE=ntfs 
/dev/sda5: UUID=9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2 TYPE=ext3  
   Jaunty /boot
/dev/sda6: UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 TYPE=ext3  
   Jaunty /
/dev/sda7: TYPE=swap UUID=a8b4289b-34b4-4c92-a7b9-c0bd7f253cff 
/dev/sda8: UUID=e186fa4e-a98c-49b9-b491-2205628c1f75 TYPE=ext3 
SEC_TYPE=ext2   (shared /home)
/dev/sda9: UUID=836c9f55-820b-4760-b2cb-81af5b6fedfe TYPE=ext4  
 Karmic /
r...@cypress:/media/disk/boot/grub# 

This was on the Karmic beta Desktop CD as of 2009-10-06. Following work
around (which will require manual editing of grub.cfg every time I run
'update-grub on Karmic) I installed grub-pc on Jaunty and found that it
did appear to produce grub.cfg compliant with a separate /boot partition
when run from that installation. I'm not certain that the Jaunty
grub.cfg is correct for Jaunty (which does not use the /boot partition.)
It produced the entry:

menuentry Ubuntu, Linux 2.6.31-12-generic (on /dev/sda9) {
set root=(hd0,9)
linux /boot/vmlinuz-2.6.31-12-generic 
root=UUID=836c9f55-820b-4760-b2cb-81af5b6fedfe ro quiet splash
initrd /boot/initrd.img-2.6.31-12-generic
}

If that uses the search line for Jaunty it will not find the kernel or
initial RAM disk as those are not in the /boot partition.

-- 
incorrectly assumes /dev/mapper/ - LVM
https://bugs.launchpad.net/bugs/413345
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 411705] Re: have run udate-grub2 and my other linux wont boot

[HankB]

I have confirmed that grub-pc did not recognize usage of the /boot partition 
for the other Linux install. I was able to boot my Jaunty install after 
changing the UUID in the search option and modifying the kernel and initial RAM 
disk file names to be relative to /boot:
102,104c102,104
   search --no-floppy --fs-uuid --set 9bdeb391-8fd9-48b1-9316-c4a00b7fa7a2
   linux /vmlinuz-2.6.28-15-generic 
root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
   initrd /initrd.img-2.6.28-15-generic
---
   search --no-floppy --fs-uuid --set 7f69072f-cea2-4ec3-bde9-81dd16744034
   linux /boot/vmlinuz-2.6.28-15-generic 
 root=UUID=7f69072f-cea2-4ec3-bde9-81dd16744034 ro quiet splash
   initrd /boot/initrd.img-2.6.28-15-generic

Following this, I installed grub-pc on Jaunty and after manually running
update-grub, I note that it found Karmic but did not include a separate
search line for that. I'm not sure it will boot Karmic using this
because I do not know if it requires the search line for those entries.
(Jaunty grub.cfg is attached.) If it uses the search specified for
Jaunty (points to separate /boot partition) it will not find the Karmic
kernel and initrd.

** Attachment added: grub.cfg produced on Jaunty
   http://launchpadlibrarian.net/33229091/grub.cfg

-- 
have run udate-grub2 and my other linux wont boot
https://bugs.launchpad.net/bugs/411705
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 411705] Re: have run udate-grub2 and my other linux wont boot

[HankB]

I may have run into the same or a similar bug - After installing Karmic
in a new partition, I can no longer boot Jaunty. I have described this
in http://ubuntuforums.org/showthread.php?t=1284332 and will attach
relevant legacy and grub2 config files below.

hba...@cypress:~$ sudo parted -l
[sudo] password for hbarta: 
Model: ATA WDC WD5000BEVT-2 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start   End SizeType  File system Flags
 1  1049kB  1574MB  1573MB  primary   ntfsboot
 2  1579MB  53.1GB  51.5GB  primary   ntfs
 3  53.1GB  63.6GB  10.5GB  primary   ntfs
 4  63.6GB  500GB   437GB   extended
 5  63.6GB  64.6GB  1045MB  logical   ext3
 6  64.6GB  85.6GB  20.9GB  logical   ext3
 9  85.6GB  96.1GB  10.5GB  logical   ext4
 7  96.1GB  100GB   4096MB  logical   linux-swap(v1)
 8  100GB   500GB   400GB   logical   ext3


hba...@cypress:~$ 

Hmmm. Only one attachment, I'll post again to add the legacy grub
config.

** Attachment added: grub.cfg as setup during Karmic install
   http://launchpadlibrarian.net/33147844/grub.cfg

-- 
have run udate-grub2 and my other linux wont boot
https://bugs.launchpad.net/bugs/411705
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 411705] Re: have run udate-grub2 and my other linux wont boot

[HankB]

Follow-up to previous post with legacy grub menu.lst

** Attachment added: legacy grub menu.lst
   http://launchpadlibrarian.net/33147990/menu.lst

-- 
have run udate-grub2 and my other linux wont boot
https://bugs.launchpad.net/bugs/411705
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 442631] Re: update-grub generates an incorrect entry

[HankB]

Please see my thread at
http://ubuntuforums.org/showthread.php?p=8063611#post8063611 to
determine if this is the same bug. It caught my eye because I was
running Jaunty with a /boot partition and installation of the Karmic
beta with grub2 left my Jaunty install unbootable. (I have not figured
out what to change to fix it.)

thanks,
hank

-- 
update-grub generates an incorrect entry
https://bugs.launchpad.net/bugs/442631
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 433500] [NEW] gvfsd memory leak

[HankB]

Public bug reported:

Binary package hint: gvfs

I found my system generally unresponsive after running overnight. I
could not get the X screen saver to respond but was able to
ctrlaltF1 to a console window, log in and run 'top' where I found
that all RAM and swap were exhausted (0 swap available) and top reported
that gvfsd was using 75% of RAM. I killed firefox (using about 10% of
RAM) and saw that gvfsd went up to about 77% in a couple of minutes. At
that point I rebooted the system to try to restore normal operation.

I'm not sure if this is related to difficulty mounting a Sansa Fuze
device earlier in the day. The device failed to mount on the first try
but mounted OK on the second attempt (plugging in the USB cable.) The
Sansa Fuze has 2GB flash and an 8GB micro-SDHC card and is new so I do
not have much experience using it with this system.

I found the following relevant thread:
http://ubuntuforums.org/showthread.php?t=1151645

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: gvfs 1.2.2-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
Uname: Linux 2.6.28-15-generic x86_64

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


** Tags: amd64 apport-bug

-- 
gvfsd memory leak
https://bugs.launchpad.net/bugs/433500
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 433500] Re: gvfsd memory leak

[HankB]

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/32109503/Dependencies.txt

-- 
gvfsd memory leak
https://bugs.launchpad.net/bugs/433500
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 433500] Re: gvfsd memory leak

[HankB]

Further information -

Earlier in the day I copied about 4GB of files from an NFS mount to the
Sansa Fuze. During the copy, my wireless connection (iwlagn, Intel 5300)
dropped and I restored it by running sudo iwconfig wlan0 down up. When
the connection resumed, the file copy (using Nautilus drag and drop)
continued automatically.

-- 
gvfsd memory leak
https://bugs.launchpad.net/bugs/433500
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

Re: [Bug 355998] Re: usb-storage: waiting for device to settle before scanning

[HankB]

On Tue, May 5, 2009 at 9:52 AM, Josef Wells
josefwe...@alumni.utexas.net wrote:

 http://cdgenp01.csd.toshiba.com/content/support/downloads/gigabeat-F10204060_OwnersManual3_02_US_UE.pdf
 (search for MTP)

 I tried to reinstall the original firmware to no avail.  I do wonder
 what lsusb would say if you changed the mode in the original firmware.

Here are the results with my Sansa e280. Rockbox leaves the original
firmware (OF) intact since it only recently got USB support.

Rockbox lsusb:
Bus 008 Device 005: ID 0781:7421 SanDisk Corp. Sansa E200 series

OF/MSC
Bus 008 Device 006: ID 0781:7421 SanDisk Corp. Sansa E200 series

OF/MTP
Bus 008 Device 007: ID 0781:7420 SanDisk Corp. Sansa E200 series (mtp)

I can confirm that the bug in 9.04 prevented my Sansa from being
mounted regardless of whether it was running Rockbox or OF/MSC. If I
switched the OF to MTP, it was mounted but copying files to it did not
work correctly. It appears that 8.10 will not mount it in MTP mode.
(Files appeared in the mounted FS regardless of firmware and did not
appear in the device when it was not mounted. But that's another
issue.)

-- 
'03 BMW F650CS - hers
'98 Dakar K12RS - BABY K grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - OUR LC
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois

-- 
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
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 345916] Re: Sandisk Sansa e250 won't connect

[HankB]

There is another bug filed for this problem:
https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/355998 That
bug report also includes a patch and directions to apply.  I have done
so and can confirm that it works for the lpia architecture.

-- 
Sandisk Sansa e250 won't connect
https://bugs.launchpad.net/bugs/345916
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 355998] Re: usb-storage: waiting for device to settle before scanning

[HankB]

I have also applied the patch and can confirm that it works for the lpia
architecture.

There is a duplicate of this bug filed under
https://bugs.launchpad.net/ubuntu/+bug/345916

thanks for the patch and instructions for how to apply it.

-- 
usb-storage: waiting for device to settle before scanning
https://bugs.launchpad.net/bugs/355998
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 345916] Re: Sandisk Sansa e250 won't connect

[HankB]

Add me to the group for whom the fixes are not permanent. This is on an
Eee PC 901 running 9.04 lpia. It initially did not mount (as with every
other 9.04 install I have performed) I fixed this by eliminating the
Sansa entries in the gphoto fdi file. Last night it stopped working. I
tried applying other fixes identified here (renaming the gphoto fdi file
and making the device ID 4 digits in the 10-usb-music-players.fdi file.)
Neither fix worked. Symptoms look the same with waiting for device to
settle  as the last line from dmesg.

I booted the regular install. (lpia runs from an SD card) This is 9.04
UNR for which I had renamed the gphpoto fdi file. It still mounts my
Sansa. Following confirmation of that, I rebooted lpia and it still will
not mount my Sansa.

Another data point, if it matters.

If there is an upstream fix, is there anyway to give it a go on a normal
9.04 install?

-- 
Sandisk Sansa e250 won't connect
https://bugs.launchpad.net/bugs/345916
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 365532] Re: USB MP3 player (Sansa) is not mounted automatically

[HankB]

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/25885508/BootDmesg.txt

** Attachment added: CurrentDmesg.txt
   http://launchpadlibrarian.net/25885509/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/25885510/Dependencies.txt

** Attachment added: HalComputerInfo.txt
   http://launchpadlibrarian.net/25885511/HalComputerInfo.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/25885512/Lspci.txt

** Attachment added: Lsusb.txt
   http://launchpadlibrarian.net/25885513/Lsusb.txt

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/25885514/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/25885515/ProcInterrupts.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/25885516/ProcModules.txt

-- 
USB MP3 player (Sansa) is not mounted automatically
https://bugs.launchpad.net/bugs/365532
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 365532] [NEW] USB MP3 player (Sansa) is not mounted automatically

[HankB]

Public bug reported:

(copied from http://ubuntuforums.org/showthread.php?p=7125705)

I have just discovered that Jaunty does not mount my USB (Mass storage)
MP3 player. The results of plugging it in is:

[CODE][ 6722.195378] usb 1-2: USB disconnect, address 11
[ 6725.958494] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 6726.166964] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 6726.548117] usb 1-2: new high speed USB device using ehci_hcd and address 15
[ 6726.700358] usb 1-2: configuration #1 chosen from 1 choice
[ 6726.741176] scsi7 : SCSI emulation for USB Mass Storage devices
[ 6726.762682] usb-storage: device found at 15
[ 6726.762697] usb-storage: waiting for device to settle before scanning
[ 6776.132166] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 406
[ 6890.466278] usb 1-2: USB disconnect, address 15
[ 6896.132171] ===rt_ioctl_giwscan. 4(4) BSS returned, data-length = 406
[ 7016.134056] ===rt_ioctl_giwscan. 3(3) BSS returned, data-length = 323
[ 7091.452097] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 7091.640402] hub 1-0:1.0: unable to enumerate USB device on port 2
[ 7092.012136] usb 1-2: new high speed USB device using ehci_hcd and address 18
[ 7092.169324] usb 1-2: configuration #1 chosen from 1 choice
[ 7092.178161] scsi8 : SCSI emulation for USB Mass Storage devices
[ 7092.200279] usb-storage: device found at 18
[ 7092.200294] usb-storage: waiting for device to settle before scanning[/CODE]

This is with Rockbox running on the MP3 but I get the same results with
the factory Sansa firmware. H/W is an Eee PC if that makes a difference.

I have mounted this on my other laptop running Intrepid to make sure it
mounts OK (and it does) with the following results from dmesg:


[CODE][414304.284104] hub 8-0:1.0: unable to enumerate USB device on port 2
[414304.488144] hub 5-0:1.0: unable to enumerate USB device on port 2
[414304.868055] usb 8-2: new high speed USB device using ehci_hcd and address 10
[414305.020071] usb 8-2: configuration #1 chosen from 1 choice
[414305.023022] scsi8 : SCSI emulation for USB Mass Storage devices
[414305.025244] usb-storage: device found at 10
[414305.025254] usb-storage: waiting for device to settle before scanning
[414310.025859] usb-storage: device scan complete
[414310.028100] scsi 8:0:0:0: Direct-Access Rockbox  Internal
Storage 0.00 PQ: 0 ANSI: 4
[414310.031457] scsi 8:0:0:1: Direct-Access Rockbox  SD Card Slot
  0.00 PQ: 0 ANSI: 4
[414310.037067] sd 8:0:0:0: [sdb] 15708160 512-byte hardware sectors (8043 MB)
[414310.040435] sd 8:0:0:0: [sdb] Write Protect is off
[414310.040442] sd 8:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[414310.040447] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[414310.050554] sd 8:0:0:0: [sdb] 15708160 512-byte hardware sectors (8043 MB)
[414310.053934] sd 8:0:0:0: [sdb] Write Protect is off
[414310.053944] sd 8:0:0:0: [sdb] Mode Sense: 0b 00 00 08
[414310.053949] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[414310.053958]  sdb: sdb1 sdb2
[414310.064326] sd 8:0:0:0: [sdb] Attached SCSI removable disk
[414310.064545] sd 8:0:0:0: Attached scsi generic sg2 type 0
[414310.073383] sd 8:0:0:1: [sdc] Attached SCSI removable disk
[414310.073538] sd 8:0:0:1: Attached scsi generic sg3 type 0[/CODE]

Other than this, I have not had any problems mounting other USB thumb
drives. Suggestions on how to resolve this would be most welcome.

Edit: I tried this using a Jaunty RC live CD on another system (Thinkpad
T42) and it also did not mount the Sansa. It normally runs Intrepid and
mounts the Sansa without difficulty.

Edit-01: I can confirm that this bug still exists with the release - at
least when installed on an Eee PC 901. I also found the same bad
behavior on eeebuntu 2.0 (based on 8.10 but with a 2.6.28 kernel, so I
suspect it is something related to the 2.6.28 kernel.

Impact - I need to keep an SDHC card with 8.10 UNR installed in my Eee
PC that I can boot to load the kernel. On my T500 and T42 I will hold
off upgrading from Intrepid to Jaunty until this has been fixed.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
MachineType: ASUSTeK Computer INC. 901
Package: linux-image-2.6.28-11-generic 2.6.28-11.42
ProcCmdLine: root=UUID=fd603e10-1ad6-4574-bd77-6db6ea2b9d40 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.28-11.42-generic
SourcePackage: linux
Tags:  ubuntu-unr

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


** Tags: apport-bug i386 ubuntu-unr

-- 
USB MP3 player (Sansa) is not mounted automatically
https://bugs.launchpad.net/bugs/365532
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 365532] Re: USB MP3 player (Sansa) is not mounted automatically

[HankB]

** Attachment added: lsusb -v with Sansa plugged in
   http://launchpadlibrarian.net/25885582/lsusb.txt

-- 
USB MP3 player (Sansa) is not mounted automatically
https://bugs.launchpad.net/bugs/365532
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

Re: [Bug 365532] Re: USB MP3 player (Sansa) is not mounted automatically

[HankB]

*** This bug is a duplicate of bug 345916 ***
https://bugs.launchpad.net/bugs/345916

How embarrassing! I searched for this bug and was unable to find it.

Many thanks! The work around works for me too and I will no longer
have to boot 8.10 to load files.

best,
hank

On Thu, Apr 23, 2009 at 8:49 AM, Benjamin_L benja...@lebsanft.org wrote:
 *** This bug is a duplicate of bug 345916 ***
    https://bugs.launchpad.net/bugs/345916

 ** This bug has been marked a duplicate of bug 345916
   Sandisk Sansa e250 won't connect

 --
 USB MP3 player (Sansa) is not mounted automatically
 https://bugs.launchpad.net/bugs/365532
 You received this bug notification because you are a direct subscriber
 of the bug.



-- 
'03 BMW F650CS - hers
'98 Dakar K12RS - BABY K grew up.
'93 R100R w/ Velorex 700 (MBD starts...)
'95 Miata - OUR LC
polish visor: apply squashed bugs, rinse, repeat
Beautiful Sunny Winfield, Illinois

-- 
USB MP3 player (Sansa) is not mounted automatically
https://bugs.launchpad.net/bugs/365532
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 345916] Re: Sandisk Sansa e250 won't connect

[HankB]

I renamed the .fdi file (tacked on .dontuse) and have mounted my
e280/Rockbox twice. :D

I hope it continues to work. This is following a fresh install of Jaunty
(not beta, not RC)

thanks,
hank

-- 
Sandisk Sansa e250 won't connect
https://bugs.launchpad.net/bugs/345916
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