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
** 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
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
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
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
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
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
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:
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
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.
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]
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
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.
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
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.
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:
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:
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
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
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.
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:
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
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
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
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
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
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
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
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
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
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
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
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.
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.
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
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
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
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
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.
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]:
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
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
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
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
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
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 -
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
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
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.
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
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
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
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:
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
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.
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
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
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:
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
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
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
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:
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
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.
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
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
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:
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
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:
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.
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:
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.
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:
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
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
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
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:
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
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:
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)
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
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:
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
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
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
1 - 100 of 263 matches
Mail list logo
