[Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

[monochromec]

Please note that the work-around only works with one swap file.
Alternatively simply hardcode the device in the above statement.

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

Title:
  dev's major/minor not captured in /sys/power/resume

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


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

[Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

[monochromec]

** Description changed:

  When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
  "Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume
  
  Current configuration:
  
  1) Legacy boot configuration (non-UEFI!)
  
  2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
  UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw  
0   0
  /swap noneswapsw,pri=2
0   0
+ 
+ (swap file is the primary and only option for hibernation as partition
+ is too small)
  
  2) resume config in /etc/initramfs-tools/conf.d/resume with the correct
  UUID and offset:
  
  RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b resume_offset=39608320
  
  (blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
  BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")
  
  3) Correct grub config:
  
  GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
  resume_offset=39608320 acpi_enforce_resources=lax"
  
  Suspect a regression issue with systemd-255 as the issue did *not*
  appear with Focal Fossal (system-245) and only surfaced after the
  upgrade to 24.04.
  
  Work-around:
  
  Amend /etc/rc.local (if this is enabled via systemd) with:
  
- "lsblk | fgrep  | cut -d' '
- -f4 >/sys/power/resume"
+ "lsblk | fgrep $(basename $(df -P $(fgrep swap /etc/fstab | grep '^/' |
+ cut -d' ' -f1) | grep '^/' | cut -d' ' -f1)) | cut -d' ' -f4
+ >/sys/power/resume"
+ 
+ Please let me know if more info is required - more than happy to help!

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

Title:
  dev's major/minor not captured in /sys/power/resume

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


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

[Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

[monochromec]

Swap file is the primary and only option  for hibernation as partition
is too small.

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

Title:
  dev's major/minor not captured in /sys/power/resume

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


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

[Bug 2061311] Re: dev's major/minor not captured in /sys/power/resume

[monochromec]

Please let me know if more info is required - more than happy to help!

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

Title:
  dev's major/minor not captured in /sys/power/resume

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


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

[Bug 2061311] [NEW] dev's major/minor not captured in /sys/power/resume

[monochromec]

Public bug reported:

When trying to configure hibernation on Noble Numbat, systemd-sleep hibernate 
complains about
"Failed to find location to hibernate to: Invalid argument" caused by a "0:0" 
entry in /sys/power/resume

Current configuration:

1) Legacy boot configuration (non-UEFI!)

2) Dual swap space configuration (/etc/fstab excerpt for swap partition and 
file):
UUID=c323a060-1b69-48af-a5bb-395f5d05fb60 noneswapsw
  0   0
/swap noneswapsw,pri=2  
  0   0

2) resume config in /etc/initramfs-tools/conf.d/resume with the correct
UUID and offset:

RESUME=UUID=7799882e-189c-484b-b9d4-f9e302859b0b resume_offset=39608320

(blkid: /dev/sda1: UUID="7799882e-189c-484b-b9d4-f9e302859b0b"
BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4f6b947f-01")

3) Correct grub config:

GRUB_CMDLINE_LINUX="resume=UUID=7799882e-189c-484b-b9d4-f9e302859b0b
resume_offset=39608320 acpi_enforce_resources=lax"

Suspect a regression issue with systemd-255 as the issue did *not*
appear with Focal Fossal (system-245) and only surfaced after the
upgrade to 24.04.

Work-around:

Amend /etc/rc.local (if this is enabled via systemd) with:

"lsblk | fgrep  | cut -d' '
-f4 >/sys/power/resume"

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

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

Title:
  dev's major/minor not captured in /sys/power/resume

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


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

[Bug 1975410] Re: Maximized window border under status bar in Wayland / Mutter

[monochromec]

Also happens with non-maximized windows (cf. attached screenshot).

** Attachment added: "Screenshot from 2022-06-05 12-33-52.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975410/+attachment/5594953/+files/Screenshot%20from%202022-06-05%2012-33-52.png

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

Title:
  Maximized window border under status bar in Wayland / Mutter

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


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

[Bug 1975410] Re: Maximized window border under status bar in Wayland / Mutter

[monochromec]

More than happy to provide more info, just 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/1975410

Title:
  Maximized window border under status bar in Wayland / Mutter

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


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

[Bug 1975410] [NEW] Maximized window border under status bar in Wayland / Mutter

[monochromec]

Public bug reported:

Cf. https://gitlab.gnome.org/GNOME/mutter/-/issues/1627

This is still present in Jammy (as it was in Impish). Were the upstream
patches included the corresponding builds?

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sun May 22 12:50:48 2022
DisplayManager: gdm3
InstallationDate: Installed on 2017-08-31 (1724 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-04-25 (26 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

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


** Tags: amd64 apport-bug jammy 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/1975410

Title:
  Maximized window border under status bar in Wayland / Mutter

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


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

[Bug 1972763] [NEW] Control sound missing for volume keys

[monochromec]

Public bug reported:

Cf. https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/508

Seems to be another regression issue with Jammy.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue May 10 07:08:40 2022
DisplayManager: gdm3
InstallationDate: Installed on 2017-08-31 (1712 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-04-25 (14 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

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


** Tags: amd64 apport-bug jammy 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/1972763

Title:
  Control sound missing for volume keys

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


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

[Bug 1948766] Re: Atril crashes on Impish regardless of PDF file

[monochromec]

Due to file size restrictions I've uploaded the file to a public server
and stated the download URL in the GH issue.

Please let me know if further information is required.

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

Title:
  Atril crashes on Impish regardless of PDF file

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1948766/+subscriptions


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

[Bug 1948766] Re: Atril crashes on Impish regardless of PDF file

[monochromec]

Yes.

lspci excerpt:

00:02.0 VGA compatible controller: Intel Corporation Iris Plus Graphics 640 
(rev 06) (prog-if 00 [VGA controller])
DeviceName:  Onboard IGD
Subsystem: Dell Iris Plus Graphics 640

and atril backtrace generated with apport-retrace -g ... :

[New LWP 954592]
[New LWP 954595]
[New LWP 954596]
[New LWP 954593]
[New LWP 954623]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `atril 
/home/christoph/ownCloud/ocl/recipes/Gruenkohl/GK1.pdf'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f615146b0f2 in ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
[Current thread is 1 (Thread 0x7f6147991ac0 (LWP 954592))]
(gdb) bt
#0  0x7f615146b0f2 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
#1  0x7f615146b200 in  () at /lib/x86_64-linux-gnu/libgtk-3.so.0
...
[goes on for another 2,000 lines]

Please let me know if the rest of the 42 MB large crash report is needed
as well.

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

Title:
  Atril crashes on Impish regardless of PDF file

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1948766/+subscriptions


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

[Bug 1948766] [NEW] Atril crashes on Impish regardless of PDF file

[monochromec]

Public bug reported:

Evince and Okular work w/o issues on the same set of PDF files

Atril version is 1.26.0-0ubuntu1 running on Xwayland 2:21.1.2-0ubuntu1.

Please let me know if you need more info.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: atril 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Oct 26 10:15:17 2021
InstallationDate: Installed on 2017-08-31 (1516 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: atril
UpgradeStatus: Upgraded to impish on 2021-10-14 (11 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

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


** Tags: amd64 apport-bug impish 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/1948766

Title:
  Atril crashes on Impish regardless of PDF file

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


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

[Bug 1942290] Re: Folding menus do not work anymore (on Wayland)

[monochromec]

This only occurs in the gnome-shell running Wayland, this problem cannot
be reproduced in other desktop environments (both running Wayland and
X11 including Cinnamon and Plasma).

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

Title:
  Folding menus do not work anymore (on Wayland)

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


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

[Bug 1942290] [NEW] Folding menus do not work anymore (on Wayland)

[monochromec]

Public bug reported:

When trying to access any folding menus (eg. in View top-level menu such
as Headers, Sort by, Threads, etc.) these menus do not expand any more.

This seems to be bound to Wayland only as it work as expected under X11
using Gnome shell.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: thunderbird 1:78.13.0+build1-0ubuntu0.21.04.2
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  christoph   6475 F pipewire-media-
 /dev/snd/seq:christoph   6474 F pipewire
BuildID: 20210802223056
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Sep  1 07:59:50 2021
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini 
or extensions.sqlite)
InstallationDate: Installed on 2017-08-31 (1461 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-0680c0c5-c5cc-4fcd-8a7f-a4cde0210404
Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/thunderbird/omni.ja:greprefs.js:732
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=78.13.0/20210802223056 (In use)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RunningIncompatibleAddons: False
SourcePackage: thunderbird
SubmittedCrashIDs:
 bp-0680c0c5-c5cc-4fcd-8a7f-a4cde0210404
 bp-8a568d4d-03fa-4892-aa74-169250210331
 bp-a3a6396d-cf62-424a-85dd-3772f0210328
 bp-5c7f6431-4927-4afd-8eca-f673e0210328
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: Upgraded to hirsute on 2021-04-23 (130 days ago)
dmi.bios.date: 06/09/2021
dmi.bios.release: 2.16
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.16.0
dmi.board.name: 0PF86Y
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.16.0:bd06/09/2021:br2.16:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

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


** Tags: amd64 apport-bug hirsute 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/1942290

Title:
  Folding menus do not work anymore (on Wayland)

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


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

[Bug 1926057] Re: nextcloud crashes with SIGSEV

[monochromec]

Bug occurred again. Creating new issue at:
https://bugs.launchpad.net/ubuntu/+filebug/69e6e0ca-b494-11eb-a1ce-
d485646cd9a4?field.title=nextcloud+crashed+with+SIGABRT

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] Re: nextcloud crashes with SIGSEV

[monochromec]

Can't reproduce the issue after a recent upgrade so it's probably safe
to close this issue. I'll open a new issue should this resurface.

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] Re: nextcloud crashes with SIGSEV

[monochromec]

Still causing SIGSEV with  3.1.1-1ubuntu1.1.

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] modified.conffile..etc.apport.crashdb.conf.txt

[monochromec]

apport information

** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/bugs/1926057/+attachment/5496216/+files/modified.conffile..etc.apport.crashdb.conf.txt

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] ProcEnviron.txt

[monochromec]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1926057/+attachment/5496215/+files/ProcEnviron.txt

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] ProcCpuinfoMinimal.txt

[monochromec]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1926057/+attachment/5496214/+files/ProcCpuinfoMinimal.txt

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] Re: nextcloud crashes with SIGSEV

[monochromec]

apport information

** Tags added: apport-collected

** Description changed:

  This does not seem to be related to
  https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053
  going by the stack trace.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: nextcloud-desktop 3.1.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr 25 10:14:37 2021
  InstallationDate: Installed on 2017-08-31 (1332 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: nextcloud-desktop
  UpgradeStatus: Upgraded to hirsute on 2021-04-23 (1 days ago)
  mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu65
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: GNOME
+ DistroRelease: Ubuntu 21.04
+ InstallationDate: Installed on 2017-08-31 (1348 days ago)
+ InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ Package: nextcloud-desktop 3.1.1-1ubuntu1.1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
+ Tags:  wayland-session hirsute
+ Uname: Linux 5.11.0-16-generic x86_64
+ UpgradeStatus: Upgraded to hirsute on 2021-04-23 (17 days ago)
+ UserGroups: audio libvirt wireshark
+ _MarkForUpload: True
+ mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1926057/+attachment/5496213/+files/Dependencies.txt

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] Re: nextcloud crashes with SIGSEV

[monochromec]

This is clearly a packaging issue as I could compile the GH master on
hirsute per the repo instructions w/o issues.

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

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1926057] [NEW] nextcloud crashes with SIGSEV

[monochromec]

Public bug reported:

This does not seem to be related to
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053
going by the stack trace.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: nextcloud-desktop 3.1.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sun Apr 25 10:14:37 2021
InstallationDate: Installed on 2017-08-31 (1332 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: nextcloud-desktop
UpgradeStatus: Upgraded to hirsute on 2021-04-23 (1 days ago)
mtime.conffile..etc.apport.crashdb.conf: 2021-04-25T10:10:15.799073

** Affects: nextcloud-desktop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute third-party-packages 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/1926057

Title:
  nextcloud crashes with SIGSEV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1926057/+subscriptions

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

[Bug 1923053] Re: [SRU] nextcloud crashed with SIGSEGV.

[monochromec]

Version 3.1.1-1ubuntu1 not work for me in hirsute.

Stack trace of thread 7682:
#0  0x7fd1dc94263f n/a (libQt5Core.so.5 + 0x2ee63f)
#1  0x7fd1dd2d75a6 
_ZN15QGuiApplication11screenAddedEP7QScreen (libQt5Gui.so.5 + 0x1345a6)
#2  0x7fd1dd2bcd80 
_ZN22QWindowSystemInterface17handleScreenAddedEP15QPlatformScreenb 
(libQt5Gui.so.5 + 0x119d80)
#3  0x7fd1d050f540 _ZN14QXcbConnection17initializeScreensEv 
(libQt5XcbQpa.so.5 + 0x72540)
#4  0x7fd1d04ea2a4 
_ZN14QXcbConnectionC2EP19QXcbNativeInterfacebjPKc (libQt5XcbQpa.so.5 + 0x4d2a4)
#5  0x7fd1d04ed10f 
_ZN15QXcbIntegrationC2ERK11QStringListRiPPc (libQt5XcbQpa.so.5 + 0x5010f)
#6  0x7fd1e9933593 n/a (libqxcb.so + 0x2593)
#7  0x7fd1dd2db9fc 
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5Gui.so.5 + 
0x1389fc)
#8  0x7fd1dd2dce88 
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5Gui.so.5 + 0x139e88)
#9  0x7fd1dc911e46 _ZN23QCoreApplicationPrivate4initEv 
(libQt5Core.so.5 + 0x2bde46)
#10 0x7fd1dd2dfe02 _ZN22QGuiApplicationPrivate4initEv 
(libQt5Gui.so.5 + 0x13ce02)
#11 0x7fd1e0c7bfed _ZN19QApplicationPrivate4initEv 
(libQt5Widgets.so.5 + 0x170fed)
#12 0x56345e20868b 
_ZN11SharedTools19QtSingleApplicationC1ERK7QStringRiPPc (nextcloud + 0x1c868b)
#13 0x56345e12930c _ZN3OCC11ApplicationC2ERiPPc (nextcloud 
+ 0xe930c)
#14 0x56345e0f53c7 main (nextcloud + 0xb53c7)
#15 0x7fd1dc10e565 __libc_start_main (libc.so.6 + 0x28565)
#16 0x56345e0f5abe _start (nextcloud + 0xb5abe)

Going by the coredumpctl generated ST, this may be a different bug. More
than happy to open a separate bug and supply more information, just 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/1923053

Title:
  [SRU] nextcloud crashed with SIGSEGV.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053/+subscriptions

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

[Bug 1912055] [NEW] FF screensharing works under Plasma but not Gnome

[monochromec]

Public bug reported:

Firefox is 84.0.2
xdg-desktop-portal is 1.8.0-1 (same as xdg-desktop-portal-gtk)
gnome-shell is 3.38.1-1ubuntu1.1
plasma-desktop is 5.19.5-0ubuntu1

(all packages per latest Groovy versions)

Another hint: Running FF offers me a selection of app windows when
starting to share the screen (for example in a Jitsi session), doing the
same under Gnome only allows me to share my entire screen.

Happy to provide more info, just let me know.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xdg-desktop-portal-gtk 1.8.0-1
ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18
Uname: Linux 5.8.0-38-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sat Jan 16 14:25:57 2021
InstallationDate: Installed on 2017-08-31 (1233 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: xdg-desktop-portal-gtk
UpgradeStatus: Upgraded to groovy on 2020-10-23 (84 days ago)

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug groovy 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/1912055

Title:
  FF screensharing works under Plasma but not Gnome

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1912055/+subscriptions

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

[Bug 1877833] Re: invisible playhead during playback

[monochromec]

This bug is also reproducible on KDE Plasma 5.18.5 and a custom build
using Audacity 2.4.1.

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

Title:
  invisible playhead during playback

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

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

[Bug 1877833] [NEW] invisible playhead during playback

[monochromec]

Public bug reported:

The little green arrow (aka playhead/recordhead) is not visible during
playback / recording in 2.3.3.

As the snap package works ok in that regard, I suspect it's a GTK3
packaging issue.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: audacity 2.3.3-1build1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
AlsaCards:
 0 [PCH]: HDA-Intel - HDA Intel PCH
   HDA Intel PCH at 0xdc428000 irq 136
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
Date: Sun May 10 09:57:12 2020
InstallationDate: Installed on 2017-08-31 (982 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: audacity
UpgradeStatus: Upgraded to focal on 2020-04-25 (14 days ago)

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


** Tags: amd64 apport-bug focal 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/1877833

Title:
  invisible playhead during playback

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

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

[Bug 1584161] Re: Freedesktop Screensaver API is not implemented

[monochromec]

Unfortunately, this has escaped regression and reared its ugly head
again in Eoan:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename:   eoan

$ gdbus call --session --dest org.freedesktop.ScreenSaver --object-path
/org/freedesktop/ScreenSaver --method
org.freedesktop.ScreenSaver.GetActive

Error: GDBus.Error:org.freedesktop.DBus.Error.NotSupported: This method
is not implemented

The same method invocation works with Gnome instead of freedesktop:

$  gdbus call --session --dest org.gnome.ScreenSaver --object-path 
/org/gnome/ScreenSaver --method org.gnome.ScreenSaver.GetActive
(false,)

According to d-feet "GetActive" exists in both interfaces of the
corresponding object path with the same signature.

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

Title:
  Freedesktop Screensaver API is not implemented

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1584161/+subscriptions

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

[Bug 1453463] Re: undefined symbol: FAMNoExists

[monochromec]

The issue is still present in 19.10.

RCA:

libfam0 (lighttpd) dependency contains a libfam.so which doesn't resolve the 
symbol in question.
Only installing gamin (as suggested above) provides a proper (in that case) 
libfam.so as part of its dependency libgamin0.

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

Title:
  undefined symbol: FAMNoExists

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

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

[Bug 1785489] Re: Mismatch between packaged version of microcode and latest microcode update as available from the store

[monochromec]

Can be closed after recent intel-microcode update
(3.20180807a.0ubuntu0.18.04.1) fixed this issue.

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

Title:
  Mismatch between packaged version of microcode and latest microcode
  update as available from the store

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1785489/+subscriptions

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

[Bug 1785489] [NEW] Mismatch between packaged version of microcode and latest microcode update as available from the store

[monochromec]

Public bug reported:

The subject says it all:

When you update the ucode via the software store / center, the ucode as
reported by /proc/cpuinfo or
/sys/devices/system/cpu/cpu1/microcode/version doesn't match the
contents of /lib/firmware/intel-ucode for the corresponding revision
anymore (0x8e vs 0x84 on my i7-7560U). Thus, tools like iucode-tools get
confused and and useful utilities such as needrestart (which are in turn
relying on the correct functioning of iucode-tool) become broken in that
respect.

Workaround: fix package contents.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: intel-microcode 3.20180425.1~ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sun Aug  5 17:02:25 2018
InstallationDate: Installed on 2017-08-31 (338 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: intel-microcode
UpgradeStatus: Upgraded to bionic on 2018-05-02 (95 days ago)

** Affects: intel-microcode (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Description changed:

  The subject says it all:
  
  When you update the ucode via the software store / center, the ucode as
  reported by /proc/cpuinfo or
  /sys/devices/system/cpu/cpu1/microcode/version doesn't match the
  contents of /lib/firmware/intel-ucode for the corresponding revision
- anymore (0x8e vs 0x84). Thus, tools like iucode-tools get confused and
- and useful utilities such as needrestart (which are in turn relying on
- the correct functioning of iucode-tool) become broken in that respect.
+ anymore (0x8e vs 0x84 on my i7-7560U). Thus, tools like iucode-tools get
+ confused and and useful utilities such as needrestart (which are in turn
+ relying on the correct functioning of iucode-tool) become broken in that
+ respect.
  
  Workaround: fix package contents.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: intel-microcode 3.20180425.1~ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Aug  5 17:02:25 2018
  InstallationDate: Installed on 2017-08-31 (338 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-microcode
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (95 days ago)

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

Title:
  Mismatch between packaged version of microcode and latest microcode
  update as available from the store

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1785489/+subscriptions

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

[Bug 1695326] Re: Firefox loader hardening

[monochromec]

It worked on the release which I flagged it for. As this doesn't surface
now, I see little point in verifying this with a working environment
which I would have to heavily tweak in order to reproduce this now.

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

Title:
  Firefox loader hardening

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

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

[Bug 1695326] Re: Firefox loader hardening

[monochromec]

Hasn't surfaces in recent releases but I haven't checked the presence of
my suggested patch in the distribution. I would recommend confirming the
above patch before closing this ticket.

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

Title:
  Firefox loader hardening

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

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

[Bug 1695326] Re: Firefox loader hardening

[monochromec]

Amazing that it only took slightly more than a year to move this from
New to Incomplete. That's the spirit for such an important project such
as FF. :-)

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

Title:
  Firefox loader hardening

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

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

[Bug 1716967] Re: Amarok causes gnome-shell to crash

[monochromec]

Please close this one as I filed a new, more fitting bug report:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1718993.

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

Title:
  Amarok causes gnome-shell to crash

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

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

[Bug 1718993] [NEW] libgjs crashes gnome-shell when using certain extenions

[monochromec]

Public bug reported:

Could this be related to
https://bbs.archlinux.org/viewtopic.php?id=227910=2?

Please escalate to upstream if they are not already aware this...

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: libgjs0f 1.48.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Fri Sep 22 20:25:25 2017
InstallationDate: Installed on 2017-08-31 (22 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gjs
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  libgjs crashes gnome-shell when using certain extenions

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

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

[Bug 1716967] Re: Amarok causes gnome-shell to crash

[monochromec]

Apparently this is caused by a rogue Gnome Shell extension. Running
gnome-shell inside a gdb session reveals the following BT after the
crash:

...

Thread 1 "gnome-shell" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58
58  ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
#0  0x7f21589ce77f in __GI_raise (sig=sig@entry=6) at 
../sysdeps/unix/sysv/linux/raise.c:58
#1  0x7f21589d037a in __GI_abort () at abort.c:89
#2  0x7f2158fef135 in g_assertion_message () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f2158fef1ca in g_assertion_message_expr () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f215b3a745c in  () at /usr/lib/gnome-shell/libgnome-shell.so
#5  0x7f21592a82f8 in g_object_run_dispose () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6  0x7f2159ad95ee in clutter_actor_destroy () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#7  0x7f21542f7e18 in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#8  0x7f21542f787a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#9  0x7f215aea2a5f in  () at /usr/lib/libgjs.so.0
#10 0x7f215aea4114 in  () at /usr/lib/libgjs.so.0
#11 0x7f2153c08cd8 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#12 0x7f2153bfe797 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#13 0x7f2153c0896b in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#14 0x7f2153c08c24 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#15 0x7f2153c09845 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#16 0x7f2153ed0297 in JS_CallFunctionValue(JSContext*, 
JS::Handle, JS::Handle, JS::HandleValueArray const&, 
JS::MutableHandle) ()
at /usr/lib/x86_64-linux-gnu/libjs.so.0
#17 0x7f215aec31c6 in gjs_call_function_value () at /usr/lib/libgjs.so.0
#18 0x7f215ae9e2e5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0
#19 0x7f215aeb603c in  () at /usr/lib/libgjs.so.0
#20 0x7f21592a1c25 in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#21 0x7f21592b3c32 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#22 0x7f21592bc88c in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#23 0x7f21592bcc6f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#24 0x7f2159ae584c in  () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#25 0x7f215b395da3 in  () at /usr/lib/gnome-shell/libgnome-shell.so
#26 0x7f21592a82f8 in g_object_run_dispose () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#27 0x7f2159ad95ee in clutter_actor_destroy () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#28 0x7f2159ae05a4 in clutter_actor_iter_destroy () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#29 0x7f2159ae0648 in  () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#30 0x7f21592a1c25 in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#31 0x7f21592b3f46 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#32 0x7f21592bc88c in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#33 0x7f21592bcc6f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#34 0x7f2159ae584c in  () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#35 0x7f21592a82f8 in g_object_run_dispose () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#36 0x7f2159ad95ee in clutter_actor_destroy () at 
/usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-0.so
#37 0x7f21542f7e18 in ffi_call_unix64 () at 
/usr/lib/x86_64-linux-gnu/libffi.so.6
#38 0x7f21542f787a in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6
#39 0x7f215aea2a5f in  () at /usr/lib/libgjs.so.0
#40 0x7f215aea4114 in  () at /usr/lib/libgjs.so.0
#41 0x7f2153c08cd8 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#42 0x7f2153bfe797 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#43 0x7f2153c0896b in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#44 0x7f2153c08c24 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#45 0x7f2153c09845 in  () at /usr/lib/x86_64-linux-gnu/libjs.so.0
#46 0x7f2153ed0297 in JS_CallFunctionValue(JSContext*, 
JS::Handle, JS::Handle, JS::HandleValueArray const&, 
JS::MutableHandle) ()
at /usr/lib/x86_64-linux-gnu/libjs.so.0
#47 0x7f215aec31c6 in gjs_call_function_value () at /usr/lib/libgjs.so.0
#48 0x7f215ae9e2e5 in gjs_closure_invoke () at /usr/lib/libgjs.so.0
#49 0x7f215aeb603c in  () at /usr/lib/libgjs.so.0
#50 0x7f21592a1c25 in g_closure_invoke () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#51 0x7f21592b3c32 in  () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#52 0x7f21592bc88c in g_signal_emit_valist () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#53 0x7f21592bcc6f in g_signal_emit () at 
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#54 

[Bug 1574122] Re: Missing dependency on python-zeitgeist package

[monochromec]

Almost one and a half years later and this is still isn't fixed?!?

It's not that this takes rocket science to address... At least we see
some progress on triaging as this only took half year :-).

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

Title:
  Missing dependency on python-zeitgeist package

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

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

[Bug 1716967] Re: Amarok causes gnome-shell to crash

[monochromec]

The gnome shell seems to be the only environment affected by this issue
- I tried Plasma, Cinnamon, XFCE and Mate. None of them crash when
Amarok exits.

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

Title:
  Amarok causes gnome-shell to crash

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

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

[Bug 1716967] [NEW] Amarok causes gnome-shell to crash

[monochromec]

Public bug reported:

The subject says it all: when quitting Amarok, the surrounding gnome-
shell is restarted.

Apparently, something sends a SIGABRT to the shell:

Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
**
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: ** AMAROK WAS STARTED 
IN NORMAL MODE. IF YOU WANT TO SEE DEBUGGING INFORMATION, PLEASE USE: **
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: ** amarok --debug   
**
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
**
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) 
are not possible
Sep 13 18:17:45 darkstar-xps gnome-shell[8058]: JS WARNING: 
[resource:///org/gnome/shell/ui/messageList.js 353]: reference to undefined 
property this._useBodyMarkup
Sep 13 18:17:45 darkstar-xps gnome-shell[8058]: JS WARNING: 
[resource:///org/gnome/shell/ui/messageList.js 386]: reference to undefined 
property this._useBodyMarkup
Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Playlist dock/Playlist::Dock) Negative sizes (200,-1) 
are not possible
Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:46 darkstar-xps kde4-amarok.desktop[8715]: 
QWidget::setMinimumSize: (Media Sources dock/BrowserDock) Negative sizes 
(200,-1) are not possible
Sep 13 18:17:46 darkstar-xps gnome-shell[8058]: Allocating size to 
ShellEmbeddedWindow 0x5564c98fe8a0 without calling 
gtk_widget_get_preferred_width/height(). How does 
the code know the size to allocate?
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: "
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: User not found
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: 
Sep 13 18:17:47 darkstar-xps kde4-amarok.desktop[8715]: "
Sep 13 18:17:50 darkstar-xps kde4-amarok.desktop[8715]: Calling appendChild() 
on a null node does nothing.
Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: amarok(8717)/kdecore 
(KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: message repeated 2 
times: [ amarok(8717)/kdecore (KConfigSkeleton) 
KCoreConfigSkeleton::writeConfig:]
Sep 13 18:17:58 darkstar-xps kde4-amarok.desktop[8715]: Calling appendChild() 
on a null node does nothing.
Sep 13 18:17:58 darkstar-xps org.gnome.Shell.desktop[8058]: **
Sep 13 18:17:58 darkstar-xps org.gnome.Shell.desktop[8058]: 
St:ERROR:st/st-bin.c:186:st_bin_dispose: assertion failed: (priv->child == NULL)
Sep 13 18:17:58 darkstar-xps gnome-session[7902]: gnome-session-binary[7902]: 
WARNING: Application 'org.gnome.Shell.desktop' killed by signal 6
Sep 13 18:17:58 darkstar-xps gnome-session-binary[7902]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 6


Amarok seems to end normally as --debug tells me but invoking it from the 
command line produces the same effect as from within the shell: it restarts.

More than happy to send more info as required.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: amarok 2:2.8.0-0ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Sep 13 18:22:05 2017
InstallationDate: Installed on 2017-08-31 (12 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: amarok
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  Amarok causes gnome-shell to crash

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

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

[Bug 1716639] Re: gnome-screensaver issue when using Wayland

[monochromec]

Using gdm instead of lightdm produces a similar issue.

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

Title:
  gnome-screensaver issue when using Wayland

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

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

[Bug 1716639] [NEW] gnome-screensaver issue when using Wayland

[monochromec]

Public bug reported:

When using a Wayland session instead of X11 from the standard lightdm-
gtk-greeter, apparently gnome-screensaver cannot establish proper GTK+
initialisation, causing the gnome-session-binary to exit and
subsequently a greeter loop where a user is unable to log in.

The following is an excerpt from the syslog:

ep 12 11:06:49 darkstar-xps dbus-daemon[2031]: Activating service 
name='org.gnome.ScreenSaver'
Sep 12 11:06:49 darkstar-xps org.gnome.ScreenSaver[2031]: Unable to init 
server: Could not connect: Connection refused
Sep 12 11:06:49 darkstar-xps gnome-screensav[2165]: Unable to initialize GTK+
S

Running an identical session without Wayland produces the expected
behaviour: a user can log into his desktop session and start working as
usual.

Removing org.gnome.SettingsDaemon.ScreensaverProxy from /usr/share
/gnome-session/sessions/gnome.session doesn't have any effect. I'm
suspecting foul play between the screensaver proxy and the screensaver
binary itself, but don't have the bandwidth to analyse the source at the
moment.

More than happy to provide more information as required - just let me
know.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-screensaver 3.6.1-7ubuntu5
ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
Uname: Linux 4.10.0-33-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 12 11:29:30 2017
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GsettingsGnomeSession:
 org.gnome.desktop.session session-name 'ubuntu'
 org.gnome.desktop.session idle-delay uint32 300
InstallationDate: Installed on 2017-08-31 (11 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-screensaver
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug zesty

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

Title:
  gnome-screensaver issue when using Wayland

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

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

[Bug 1547762] Re: "SSL Protocol Error" in Chromium for several Google web sites after installing Ubuntu Security Updates for libnss3

[monochromec]

Sorted as Chromium was accidentally using Firefox's libnss3 library.
After a suitable tweaking it's fixed.

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

Title:
  "SSL Protocol Error" in Chromium for several Google web sites after
  installing Ubuntu Security Updates for libnss3

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1547762/+subscriptions

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

[Bug 1695326] [NEW] Firefox loader hardening

[monochromec]

Public bug reported:

If the ld cache configuration is wrong, the correct shared objects
contained in the package are never found or wrong versions being picked
up.

Example:

libnss3 is defined by a quite a few packages including Thunderbird, libnss3 and 
Firefox.
Depending on the particular linker cache config, the wrong version may be 
picked up.

Mitigation: enhance /usr/bin/firefox to explicitely include the correct
path of its shared objects in the loader path (cf. attached patch).

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

** Patch added: "tmp"
   https://bugs.launchpad.net/bugs/1695326/+attachment/4887992/+files/tmp

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

Title:
  Firefox loader hardening

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

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

[Bug 1547762] Re: "SSL Protocol Error" in Chromium for several Google web sites after installing Ubuntu Security Updates for libnss3

[monochromec]

Can confirm that this issue has surfaced once again after the update to
17.04.

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

Title:
  "SSL Protocol Error" in Chromium for several Google web sites after
  installing Ubuntu Security Updates for libnss3

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1547762/+subscriptions

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

[Bug 1670171] [NEW] Import SVG in Libreoffice Impress fails

[monochromec]

Public bug reported:

When importing an SVG in Impress, the image is displayed as blank dark grey 
rectangle.
The SVG is OK as it's correctly displayed in Inkscape.

Converting this SVG into PNG (for example with Imagemagick) works as a
work-around.

Let me know if more information is needed - more than happy to supply
what's required.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: libreoffice 1:5.2.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17
Uname: Linux 4.8.0-40-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
Date: Sun Mar  5 19:14:02 2017
InstallationDate: Installed on 2014-04-26 (1044 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to yakkety on 2016-10-14 (142 days ago)

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


** Tags: amd64 apport-bug yakkety

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

Title:
  Import SVG in Libreoffice Impress fails

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

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

[Bug 1640200] Re: 16.10 hangs on shutdown

[monochromec]

As already suspected, a kernel upgrade as suggested by Joseph didn't
change anything wrt to the issue. It would be great if we can give more
specific advice rather than suggesting a vanilla kernel upgrade as a
"one cure for all".

@Joseph: When can the community expect an increase in severity as
requested above? Given the number of affected people for this and the
previous bug (#1464917) and the timeline so far without much progress it
would be great if we can prioritize this upstream.

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

Title:
  16.10 hangs on shutdown

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

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

[Bug 1640200] Re: 16.10 hangs on shutdown

[monochromec]

This issue has been around my stock Ubuntu installation at least since
15.04 and continues to persist after the upgrade to 16.10. I have tried
all the workarounds of #1464917 without success.

I have my doubts that the kernel upgrade as suggested by Joseph will
remedy the situation but will give it a try and report back.

Given the severity of this and the old issue especially in production
environments, it would be great if we can bump up the importance.

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

Title:
  16.10 hangs on shutdown

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

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

[Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

[monochromec]

Hi David,

As this issue is still persisting (and none of the above work-arounds
worked for me): What's the bug # of the new bug you filed a few days
ago?

Thanks for your help!

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

Title:
  reboot hangs at 'Reached target Shutdown'

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

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

[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

[monochromec]

Hi Karen,

The location of the patch directory is as outlined above on 16.04. Please
double-check that you have installed the correct version of the package (this 
should
be 6.30.223.248+bdcom). Otherwise, please post the contents of your /usr/src 
directory to progress
this further.

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Bug 1593249] [NEW] snapd.refresh starts too early

[monochromec]

Public bug reported:

snapd.refresh.service starts too early before network stack is full
operational

Fix:

replace

"After=network.target"

with

"After=network-online.target"

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

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

Title:
  snapd.refresh starts too early

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

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

[Bug 1585765] Re: GPU driver problem with i915 driver

[monochromec]

Sorry, wrong kernel version. The correct version is 4.4.0-22-generic
which came as part of a normal update from the repo.

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

Title:
  GPU driver problem with i915 driver

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

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

[Bug 1585765] Re: GPU driver problem with i915 driver

[monochromec]

Issue disappeared with latest 4.4.2 kernel update.

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

Title:
  GPU driver problem with i915 driver

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

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

[Bug 1585765] [NEW] GPU driver problem with i915 driver

[monochromec]

Public bug reported:

First observed on freedesktop.org:
https://bugs.freedesktop.org/show_bug.cgi?id=94002

Steps to reproduce:

1) Suspend machine
2) Wake it back up
3) X11 crashes and takes E17 with it.

Environment:

- Kernel: 4.4.0-22-generic (stock)
- E17
- Otherwise: stock 16.04

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  root   9443 F pommed
  christoph  13343 F pulseaudio
Date: Wed May 25 21:12:14 2016
HibernationDevice: RESUME=UUID=b3b2afbf-edea-40c5-9506-44b7f0cbf4d2
InstallationDate: Installed on 2014-04-26 (760 days ago)
InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
MachineType: Apple Inc. MacBookPro8,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \boot\vmlinuz-4.4.0-22-generic ro irqpoll 
root=UUID=6a0139c1-488b-49e1-adee-a520c44dd9ab 
initrd=boot\initrd.img-4.4.0-22-generic
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic  N/A
 linux-firmware1.157
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-04-22 (33 days ago)
dmi.bios.date: 10/26/15
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.0047.B2C.1510261540
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-94245B3640C91C81
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245B3640C91C81
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B2C.1510261540:bd10/26/15:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
dmi.product.name: MacBookPro8,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug xenial

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

Title:
  GPU driver problem with i915 driver

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

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

[Bug 121362] Re: nm-applet thinks it's connected to the wired network, when it's connected to the wireless network

[monochromec]

PS: nm-applet shows the following error message: "(nm-applet:563): nm-
applet-CRITICAL **: get_menu_item_for_ap: assertion 'dup_data.hash !=
NULL' failed"

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

Title:
  nm-applet thinks it's connected to the wired network, when it's
  connected to the wireless network

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/121362/+subscriptions

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

[Bug 121362] Re: nm-applet thinks it's connected to the wired network, when it's connected to the wireless network

[monochromec]

This bug (or a similar one) surfaced in version 1.1.93-1ubuntu1 once
again. Work-around: restart nm-applet after resume as within user
desktop session.

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

Title:
  nm-applet thinks it's connected to the wired network, when it's
  connected to the wireless network

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/121362/+subscriptions

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

[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

[monochromec]

In case you are running on problems with the NetworkManager (version
1.0.4-ubuntu5) after the official upgrade to Wily (messages "[platform
/nm-linux-platform.c:2782] do_change_link(): platform-linux: do-change-
link: failure changing link 4: No such device (31)" or similar) after
wakeup from a suspend, simply restart the NetworkManager with a suitable
script in /lib/systemd/system-sleep in order to get autoconnect working
again.

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1415880/+subscriptions

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

[Bug 1415880] Re: 14e4:4365 bcmwl-kernel source: fix for null pointer crash

[monochromec]

Please note that the null pointer crash is only required for kernels =
3.18. I can confirm that the patch is working on both unicorn and vivid
releases.

@Hugo: Just follow the instructions at the beginning of the bug report A
somewhat different approach using dkms is described in a duplicate bug
report I filed some time ago
(https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789).

@PierreF: I had similar problems when suspending a MBP (which uses a BCM
4331), albeit the driver would stop working rather then causing a kernel
panic upon wake-up. Removing the driver before suspending and inserting
it once again upon wake-up did the trick for me. The implementation of
this is straight forward: just put a similar script to the following in
/lib/systemd/system-sleep

#!/bin/bash
MA=$(uname -r | awk -F'.' '{ print $1 }')
if [ $MA -ge 4 ] ; then
if [ $1 = pre ] ; then
rmmod wl
else
modprobe wl
fi
fi

Cf. for the systemd power management documentation for the details.

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

Title:
  14e4:4365 bcmwl-kernel source: fix for null pointer crash

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

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

[Bug 1474584] [NEW] Android kitkat or lollipop device is not detected

[monochromec]

Public bug reported:

Neither kitkat nor lollipop devices are detected by kernel version
4.0.1-040001-generic.

An excerpt of the log shows the following:

Jul 15 00:22:20 MBP-ubuntu kernel: usb 1-1.3: new full-speed USB device number 
67 using ehci-pci
Jul 15 00:22:20 MBP-ubuntu kernel: usb 1-1.3: device not accepting address 66, 
error -32
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: new full-speed USB device number 
66 using ehci-pci
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: device descriptor read/64, error 
-32
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: device descriptor read/64, error 
-32
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: new full-speed USB device number 
65 using ehci-pci
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: device descriptor read/64, error 
-32
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: device descriptor read/64, error 
-32
Jul 15 00:22:19 MBP-ubuntu kernel: usb 1-1.3: new full-speed USB device number 
64 using ehci-pci

There are various workarounds suggesting to remove any corresponding *hci_hcd* 
kernel modules but
as USB support is compiled statically into the kernel this doesn't seem to be 
an option.

Android version examined: 4.4.2 and 5.0.2.

Let me know if more information is needed.

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


** Tags: android usb

** Tags added: android usb

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

Title:
  Android kitkat or lollipop device is not detected

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

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

[Bug 1465933] Re: gwenview error: URL not found on startup

[monochromec]

Other people have confirmed this too for this particular version:
https://bugs.kde.org/show_bug.cgi?format=multipleid=343997.

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

Title:
  gwenview error: URL not found on startup

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

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

[Bug 1465933] [NEW] gwenview error: URL not found on startup

[monochromec]

Public bug reported:

When invoking gwenview, it displays the error message URL ... not
found.

Doesn't happen when using version 5.0.0 built from the source code.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: gwenview 4:14.12.3-0ubuntu1
Uname: Linux 4.0.1-040001-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
Date: Wed Jun 17 06:53:58 2015
InstallationDate: Installed on 2014-04-26 (416 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
SourcePackage: gwenview
UpgradeStatus: Upgraded to vivid on 2015-04-24 (53 days ago)

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


** Tags: amd64 apport-bug third-party-packages vivid

** Bug watch added: KDE Bug Tracking System #343997
   https://bugs.kde.org/show_bug.cgi?id=343997

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

Title:
  gwenview error: URL not found on startup

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

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

[Bug 1465933] Re: gwenview error: URL not found on startup

[monochromec]

Running kbuildsycoca5 to recreate the KService desktop file system
configuration cache fixes the problem.

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

Title:
  gwenview error: URL not found on startup

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Moritz,

Instead of waiting for the upstream packagers to fix this, try one of
the following:

- Use a pre-3.18 kernel. 3.16.33 and 3.16.34 are quite stable,
- Install the bmcwl package (version 6.30.233.248) and apply the patch manually 
in the /usr/src hierarchy which dkms uses to build the module. Don't forget to 
change the dkms.conf file to reflect the increased number of patches.

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1458593] Re: Super-slow startup and sluggish performance when using the GCAL provider

[monochromec]

Should have checked the Mozilla bug tacker first :-).

This bug seems to be a known issue:
https://bugzilla.mozilla.org/show_bug.cgi?id=733039.

After cleaning up the cache as suggested in the thread as a workaround,
performance is back to normal.


** Bug watch added: Mozilla Bugzilla #733039
   https://bugzilla.mozilla.org/show_bug.cgi?id=733039

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=733039
   Importance: Unknown
   Status: Unknown

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

Title:
  Super-slow startup and sluggish performance when using the GCAL
  provider

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

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

[Bug 1458593] [NEW] Super-slow startup and sluggish performance when using the GCAL provider

[monochromec]

Public bug reported:

After upgrading to 31.7 I noticed start-up times around 30 seconds when
the Google provider (version 1.0.4) in connection with Lightning is used
(I disabled the plugin temporarily for root cause analysis). Downgrading
TB to 31.6  didn't solve the problem, neither did downgrading the
Provider plugin to 1.0.3.

Let me know if more details are needed.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: thunderbird 1:31.7.0+build1-0ubuntu0.15.04.1
Uname: Linux 4.0.1-040001-generic x86_64
NonfreeKernelModules: wl
AddonCompatCheckDisabled: False
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  root751 F pommed
  christoph   5608 F pulseaudio
BuildID: 20150511105107
Channel: Unavailable
Date: Mon May 25 16:36:15 2015
ForcedLayersAccel: False
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-04-26 (394 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
IpRoute:
 default via 192.168.2.1 dev wlan0  proto static  metric 1024 
 192.168.2.0/24 dev wlan0  proto kernel  scope link  src 192.168.2.33
NoProfiles: True
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RunningIncompatibleAddons: False
SourcePackage: thunderbird
UpgradeStatus: Upgraded to vivid on 2015-04-24 (30 days ago)
dmi.bios.date: 01/24/12
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.0047.B27.1201241646
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-94245B3640C91C81
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245B3640C91C81
dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
dmi.product.name: MacBookPro8,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug third-party-packages vivid

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

Title:
  Super-slow startup and sluggish performance when using the GCAL
  provider

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Thanks for your feedback, Ralph - much appreciated!

I've found a solution for this bug. When research recent changes to the
WL module source code, I came across a Fedora patch for kernel versions
3.18 and later (https://gist.github.com/hobarrera/ac0e6225210ac5bb13f6
#file-broadcom-sta-6-30-223-248-linux-3-18-null-pointer-crash-patch).
After incorporating this patch in the DKMS hierarchy for the affected
kernels (see above), the module builds and works OK.

I attach the corresponding patch file - please incorporate this fix in
the bcmwl package asap (and don't forget to adjust dkms.conf accordingly
:-).


** Patch added: Patch for kernel versions 3.18 and later
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789/+attachment/4402262/+files/0018-linux-3.18-null-pointer.patch

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Hey Ralph,

Thanks for your feedback. While the issue is in the process of being
narrowed down - would it be possible for you to supply the following
information:

- Version of the kernel you're using alongside the distro version,
- Version of the wl module (you can get this with apt-cache showpkg 
bcmwl-kernel-source if you installed it from a repo),
- And most importantly. the exact TP-Link model which you are using alongside 
its software version (including whether you're using the stock software that 
came with the device or any third-party software such as OpenWRT, etc).

Thanks in advance for your help  feedback!

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

I was able to reproduce the issue on a stock Jessie install on a Vostro
1320 (featuring a BCM 3412). Kernel versions after 3.17 (including
3.18.12, 3.19.0, 3.19.6 and 4.0.1, at least these are the ones I checked
myself) seem to have an issue which causes the kernel to lock up.
BCM4331 causes an immediate freeze, whereas BCM 1312 (and as ralphb
pointed out above BCM 4360) only show these symptoms after actual
payload transmission. This goes for bcmwl versions 6.30.223.248 and
6.20.155.1.

I heard at a LUG meeting that Fedora 21/22 apparently contain special
patches which at least support an MBP mid-2013. I will verify this and
report results back asap.

Given that the kernel maintainer closed this issue (a move which I can
only follow partly as wl works fine on pre-3.18 kernels) and BCM chips
are pretty popular among laptop manufacturers: Could somebody upstream
please assign this and bump it up so that we can get a resolution
quickly?

More than happy to provide additional information in the meantime - just
let me know what is needed (unfortunately, the wl driver doesn't seem to
support debugging information generation beyond the usual).

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Kernel maintainer closed issue, referring back to Broadcom. I guess that
leaves the responsibility with the package maintainer. As b43 is still
showing the group temporal key issue rendering it essentially unusable
in the current kernel line (confirmed on 3.19 and 4.0.1), it would be
great if we could treat this bug with high priority.

Let me know if you need more information - more than happy to resolve
this asap.

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Driver bug confirmed.

I'll open bugzilla bug report on kernel.org with the details.

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Bugzilla bug: https://bugzilla.kernel.org/show_bug.cgi?id=97881

** Bug watch added: Linux Kernel Bug Tracker #97881
   http://bugzilla.kernel.org/show_bug.cgi?id=97881

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

As a kludge (I wouldn't go as far as calling it a proper workaround),
it's possible to substitute the wl LKM with the FOSS b43 LKM.

Assuming both b43-fwcutter and firmware-b43-installer (/ b43-legacy-
installer) are installed, you can use a slightly modified version of
boradcom-sta.conf in /etc/modprobe.d to load either b43 or wl depending
on your kernel version. Just ensure that you enable wl in your
/etc/modules file and NOT b43.

** Attachment added: broadcom-sta.conf
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789/+attachment/4392035/+files/broadcom-sta.conf

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] [NEW] bcmwl causes system freeze

[monochromec]

Public bug reported:

I'll file a bugzilla port on kernel.org with the kernel logs and post
the reference here asap.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu2 [modified: 
usr/src/bcmwl-6.30.223.248+bdcom/dkms.conf]
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
Date: Tue May  5 13:18:34 2015
InstallationDate: Installed on 2014-04-26 (373 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2)
SourcePackage: bcmwl
UpgradeStatus: Upgraded to vivid on 2015-04-24 (10 days ago)

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


** Tags: amd64 apport-bug vivid

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

When trying to reproduce the issue, I noticed that I could log into the
GUI as created by the session manager (lightdm) if I left the cable in
the onboard NIC. That means the system does go ahead when it can at
least create one network connection other than lo (which is the default
auto in my 15.04 configuration). If the NIC is not connected, the system
will exhibit the symptoms as described above.

I attach both kernel logs (with and without a cable attached). More than
happy to open a kernel bug report although that I do not think that this
is solely a kernel issue. Please advise.

The last kernel version known to work is 3.17.8-031708; any later
version up to 4.0.1 as installed from the Ubuntu kernel mainline archive
fails with the symptoms described above. I also tried to reproduce this
on version 4.1 but couldn't due to a GPL licensing issue (cf.
https://github.com/longsleep/bcmwl-ubuntu/issues/2).

** Attachment added: Kernel log without cable attached
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789/+attachment/4391329/+files/3.19.0-15.dmp

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Kernel log with cable attached to NIC.

** Attachment added: 3.19.0-15.nic.dmp
   
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1451789/+attachment/4391330/+files/3.19.0-15.nic.dmp

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1451789] Re: bcmwl causes system freeze

[monochromec]

Needless to say, the above information doesn't reflect the system state
as I had to remove the wl kernel module in order to file this issue.
Watch out for the kernel logs on bugzilla.kernel.org

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

Title:
  bcmwl causes system freeze

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

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

[Bug 1447788] Re: Bcmwl-kernel-source doesn't compile against 4.0

[monochromec]

Duplicate of # 1424676
(https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1424676). See
other bug report for issue resolution.

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

Title:
  Bcmwl-kernel-source doesn't compile against 4.0

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

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

[Bug 1448458] Re: 3.19.15 crashes on MBP 8,1

[monochromec]

Got to the bottom of this: root cause was a heavily hacked version of
BCMWL (6.20)  which I manually introduced in Trusty due to the severe
shortcomings / instability of both the FOSS b43 driver and the repo
version of Broadcoms hybrid driver (which I think was version 6.30 at
the time). A re-installation of the relevant broadcom-sta packages from
the Vivid repo fixed this problem and reintroduced stability for the
kernel once again.

BTW: The DKMS version of the package broadcom-sta-dkms doesn't compile
on the Vivid stock kernel (3.19.0-15), due to header incompatibilities,
I'll open a new bug report for this. Let me know if I should do the same
on kernel.org.

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1439616] Re: broadcom-sta-dkms 6.30.223.248-3 won't install on Vivid 15.04 Beta 2

[monochromec]

broadcom-sta-dkms module compilation error is still around in 15.04
final. Installation of broadcom-sta-common (which removes broadcom-sta-
dkms) solves the problem.

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

Title:
  broadcom-sta-dkms 6.30.223.248-3 won't install on Vivid 15.04 Beta 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1439616/+subscriptions

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

[Bug 1448458] Re: 3.19.15 crashes on MBP 8,1

[monochromec]

Downloaded and installed 4.1 as suggested. Unfortunately not working
with similar symptoms. I attach the kernel log for reference.

** Attachment added: boot.4.1.dmp
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448458/+attachment/4385911/+files/boot.4.1.dmp

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] WifiSyslog.txt

[monochromec]

apport information

** Attachment added: WifiSyslog.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384027/+files/WifiSyslog.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] UdevLog.txt

[monochromec]

apport information

** Attachment added: UdevLog.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384026/+files/UdevLog.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] ProcEnviron.txt

[monochromec]

apport information

** Attachment added: ProcEnviron.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384021/+files/ProcEnviron.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] UdevDb.txt

[monochromec]

apport information

** Attachment added: UdevDb.txt
   https://bugs.launchpad.net/bugs/1448458/+attachment/4384025/+files/UdevDb.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] JournalErrors.txt

[monochromec]

apport information

** Attachment added: JournalErrors.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384017/+files/JournalErrors.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] RfKill.txt

[monochromec]

apport information

** Attachment added: RfKill.txt
   https://bugs.launchpad.net/bugs/1448458/+attachment/4384024/+files/RfKill.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] ProcInterrupts.txt

[monochromec]

apport information

** Attachment added: ProcInterrupts.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384022/+files/ProcInterrupts.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] IwConfig.txt

[monochromec]

apport information

** Attachment added: IwConfig.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384016/+files/IwConfig.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] Re: 3.19.15 crashes on MBP 8,1

[monochromec]

apport information

** Tags added: apport-collected vivid

** Description changed:

  Installation of 3.19.15 as part of Vivid upgrade causes machine to
  freeze after Lightdm has displayed login screen. Trackpad / keyboard /
  USB mouse don't work, machine isn't visible on network. Same happens
  with kernel versions 4.0, 4.0rc7 from the Ubuntu mainline kernel repo.
  Fan spins up audibly after 30 seconds of login screen display.
  
  Kernel versions 3.16.0-33 and 3.16.0-34 work out of the box.
+ --- 
+ ApportVersion: 2.17.2-0ubuntu1
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  root731 F pommed
+ DistroRelease: Ubuntu 15.04
+ HibernationDevice: RESUME=UUID=b3b2afbf-edea-40c5-9506-44b7f0cbf4d2
+ InstallationDate: Installed on 2014-04-26 (364 days ago)
+ InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release amd64 
(20140416.2)
+ MachineType: Apple Inc. MacBookPro8,1
+ NonfreeKernelModules: wl
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: \boot\vmlinuz-3.16.0-34-generic ro 
root=UUID=6a0139c1-488b-49e1-adee-a520c44dd9ab  quiet splash 
initrd=boot\initrd.img-3.16.0-34-generic
+ ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-3.16.0-34-generic N/A
+  linux-backports-modules-3.16.0-34-generic  N/A
+  linux-firmware 1.143
+ Tags:  vivid
+ Uname: Linux 3.16.0-34-generic x86_64
+ UpgradeStatus: Upgraded to vivid on 2015-04-24 (0 days ago)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 01/24/12
+ dmi.bios.vendor: Apple Inc.
+ dmi.bios.version: MBP81.88Z.0047.B27.1201241646
+ dmi.board.asset.tag: Base Board Asset Tag#
+ dmi.board.name: Mac-94245B3640C91C81
+ dmi.board.vendor: Apple Inc.
+ dmi.board.version: MacBookPro8,1
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Apple Inc.
+ dmi.chassis.version: Mac-94245B3640C91C81
+ dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:
+ dmi.product.name: MacBookPro8,1
+ dmi.product.version: 1.0
+ dmi.sys.vendor: Apple Inc.

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384013/+files/AlsaInfo.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] CRDA.txt

[monochromec]

apport information

** Attachment added: CRDA.txt
   https://bugs.launchpad.net/bugs/1448458/+attachment/4384014/+files/CRDA.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] CurrentDmesg.txt

[monochromec]

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384015/+files/CurrentDmesg.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] Lsusb.txt

[monochromec]

apport information

** Attachment added: Lsusb.txt
   https://bugs.launchpad.net/bugs/1448458/+attachment/4384019/+files/Lsusb.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] ProcCpuinfo.txt

[monochromec]

apport information

** Attachment added: ProcCpuinfo.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384020/+files/ProcCpuinfo.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] Lspci.txt

[monochromec]

apport information

** Attachment added: Lspci.txt
   https://bugs.launchpad.net/bugs/1448458/+attachment/4384018/+files/Lspci.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] Re: 3.19.15 crashes on MBP 8,1

[monochromec]

As I had removed 4.0rc7 already when running apport, here's the kernel
log as far as I could retrieve from journalctl.

** Attachment added: 4.0rc kernel log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448458/+attachment/4384028/+files/4.0rc7

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] ProcModules.txt

[monochromec]

apport information

** Attachment added: ProcModules.txt
   
https://bugs.launchpad.net/bugs/1448458/+attachment/4384023/+files/ProcModules.txt

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] Re: 3.19.15 crashes on MBP 8,1

[monochromec]

Running apport from 3.16.0-34.

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] [NEW] 3.19.15 crashes on MBP 8,1

[monochromec]

Public bug reported:

Installation of 3.19.15 as part of Vivid upgrade causes machine to
freeze after Lightdm has displayed login screen. Trackpad / keyboard /
USB mouse don't work, machine isn't visible on network. Same happens
with kernel versions 4.0, 4.0rc7 from the Ubuntu mainline kernel repo.
Fan spins up audibly after 30 seconds of login screen display.

Kernel versions 3.16.0-33 and 3.16.0-34 work out of the box.

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

** Description changed:

  Installation of 3.19.15 as part of Vivid upgrade causes machine to
  freeze after Lightdm has displayed login screen. Trackpad / keyboard /
  USB mouse don't work, machine isn't visible on network. Same happens
  with kernel versions 4.0, 4.0rc7 from the Ubuntu mainline kernel repo.
+ Fan spins up audibly after 30 seconds of login screen display.
  
  Kernel versions 3.16.0-33 and 3.16.0-34 work out of the box.

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1448458] Re: 3.19.15 crashes on MBP 8,1

[monochromec]

Here's the kernel.org URL:

https://bugzilla.kernel.org/show_bug.cgi?id=97251


** Bug watch added: Linux Kernel Bug Tracker #97251
   http://bugzilla.kernel.org/show_bug.cgi?id=97251

** Changed in: linux (Ubuntu)
   Status: Incomplete = Confirmed

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

Title:
  3.19.15 crashes on MBP 8,1

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

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

[Bug 1234252] Re: [MacBookPro8, 1, CS4206] Left speaker low volume and absence of low freqs

[monochromec]

Same situation in 14.10.

Is anybody upstream looking at this?

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

Title:
  [MacBookPro8,1, CS4206] Left speaker low volume  and absence of low
  freqs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1234252/+subscriptions

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