I tested
https://launchpad.net/ubuntu/+source/rclone/1.50.2-2ubuntu0.1/+build/23542458
and it solves the problem.
Specifically:
- I had installed upstream build 1.56.0 to work around the problem, which was
working fine.
- I uninstalled that version, and installed Ubuntu's 1.50.2-2, and
Public bug reported:
rclone version v1.56.0 (or at least, a beta release of that version) is
required to fix rclone to adapt to a recent change in the Google Drive
API. Older versions, such as the currently packaged 1.50.2-2 on focal,
fail with the following error on some files:
ERROR :
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1858615
contains the comments indicating which git commit fixed this in the
Ubuntu packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me, this issue has now been resolved; I assume due to the pulseaudio
package updates that I installed yesterday, but it might have been fixed
for a few days longer.
** Changed in: alsa-driver (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a
Sorry, please ignore my previous comment (comment 6); I'd copied the
netplan config from another machine and adjusted all the IPs, but forgot
to change the interface name, so the entries were ignored.
Basic IP connectivity was working since I have an encrypted volume
that's unlocked via the
Uggh. On a second system that I upgraded 16.04->18.04->20.04, I have
netplan installed and a configuration file in place. However, the DNS
entry in the netplan config is ignored, so even switching to netplan
doesn't fix this bug:-(
--
You received this bug notification because you are a member
I need to communicate with an Ubuntu 16.04 server, from an Ubuntu 20.04
system. On 20.04, I tried installing the Unison packages from 20.04,
18.04, and 16.04. None of those worked:-( However, before I upgraded
that system I was running 18.04 on it, and communicating with the same
16.04 server just
The system has resolvconf 1.82 installed. /etc/resolv.conf claims that
it's generated by resolvconf, at least after I switched the system to
netplan, and I'm pretty sure it did before to. I also have ifupdown
0.8.35ubuntu1 installed.
A thought on deprecation: A deprecated package is simply
Switching to netplan does avoid this issue, but doesn't directly solve
it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883412
Title:
20.04: DNS servers from /etc/network/interfaces not honored
Oh, and /etc/resolv.conf contains:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the
Public bug reported:
I have a server that uses /etc/network/interfaces to configure static IP
info, including DNS, via /etc/network/interfaces. This worked fine in
16.04 and 18.04. However, when I updated to 20.04 this no longer works;
I have to run "systemd-resolve --set-dns=192.168.63.1
My headset (which works fine) is USB.
Which bug do you believe this is a duplicate of? I did find something
similar, but it was on 16.04, and my issue is definitely a regression
between 18.04 and 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I ran alsa-info before/after running "sudo alsa force-reload" to see if
there were any obvious differences in the output. While there are a few
differences, nothing really stands out as causing this issue.
** Attachment added: "diff for alsa-info output before/after reloading alsa"
Public bug reported:
I had Ubuntu 18.04 installed, running XFCE (Xubuntu session), and audio
worked fine, using either the built-in speakers/mic on the laptop or via
a USB headset when that was plugged in.
However, after upgrading to 20.04, the built-in audio device is no
longer available until
Is there any chance of importing the fix from Debian?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
To manage notifications about this bug go to:
** Bug watch added: Debian Bug tracker #946911
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946911
** Also affects: dmidecode (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946911
Importance: Unknown
Status: Unknown
--
You received this bug notification
Is there any chance of taking this patch into Ubuntu 18.04? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
To manage notifications about this
Oops. Ubuntu 18.04 has dmidecode 3.0 not 3.1; this patch should work
with that version (at least, it applies against unpatched upstream 3.0
anyway).
** Patch added: "0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch"
The upstream patch (which was made after upstream release 3.2) back-
ported to upstream 3.1 release (Ubuntu 18.04 contains dmidecode 3.1); it
should presumably apply cleanly to Ubuntu's dmidecode-3.1 source.
** Patch added: "0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch"
This bug is actually fixed in the dmidecode source code:
(links removed in case that's why launchpad won't let me save this comment).
Can we please back-port this fix into Ubuntu 18.04 AArch64? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The upstream commit is:
http://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode
The upstream bug report is:
savannah.nongnu.org dmidecode bug 109697
(launchpad won't let me paste the whole link)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing
> Reading illegal memory should not crash the system
I think this depends on what the memory is.
I agree 100% for any application-level memory (stuff from regular APIs
like sbrk() or mmap() etc.).
In this case, the application opens /dev/mem, which allows it to access
arbitrary physical memory
*** This bug is a duplicate of bug 1773383 ***
https://bugs.launchpad.net/bugs/1773383
Yes, the kernel upgrade solved this problem. Odd that launchpad didn't
find the duplicate bug while I was filing mine; it usually does.
--
You received this bug notification because you are a member of
Public bug reported:
[swarren@swarren-lx1 ~]$ sudo iotop
Traceback (most recent call last):
File "/usr/sbin/iotop", line 17, in
main()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 620, in main
main_loop()
File "/usr/lib/python2.7/dist-packages/iotop/ui.py", line 610,
I did upgrade my system from 14.04 (where I don't recall having these
error messages) to 16.04 long ago (and I think I filed this bug right
after the upgrade). I get these messages most/all times times that I run
"apt dist-upgrade". I think I have an EFI system partition on my Windows
disk. I have
For my own understanding, I'm curious:
a) Whether Ubuntu toolchains are usually updated for bugs like this
b) Roughly how often toolchain updates are usually released. I suppose
you're busy with Spectre stuff right now though?
--
You received this bug notification because you are a member of
Public bug reported:
gas in binutils 2.26 contains a bug that prevents compilation of ARM
Trusted Firmware in particular, or any code that references the "."
symbol following a .align statement that specifies explicit padding
data.
ATF bug report:
I found that my system had a /usr/sbin/policy-rc.d script which denied
all daemon start/restart. I have no idea where that came from, so I
deleted it and attempted to re-run the package configure.
The first attempt failed:
==
[swarren@swarren-lx1 etc]$ sudo dpkg -a --configure
Setting up
Public bug reported:
On 14.04 using "deb http://ppa.launchpad.net/ubuntu-lxc/lxd-
stable/ubuntu trusty main", I receive package lxd
2.3-0ubuntu7~ubuntu14.04.1~ppa1, and the upgrade fails with the
following messages:
==
[root@swarren-lx1 sources.list.d]# dpkg -a --configure
Setting up lxd
Do containers ever communicate back out to their host for services? If
so, perhaps the 1st-level container could ask the host lxd to help it to
pass on the device? I know lxd is at least aware when its nested and
unprivileged since "lxd init" mentions this; perhaps communication to
the outside
Public bug reported:
"lxc config device add ..." succeeds from the host to a container. Doing
the same from that container into a nested container fails.
swarren@cam:~$ ls -l /dev/ttyUSB0
crw-rw 1 root dialout 188, 0 Apr 23 20:46 /dev/ttyUSB0
swarren@cam:~$ sudo picocom -b 115200
The link to the Debian source package commit that fixed this is:
https://sourceforge.net/p/shorewall/debian/ci/84faab9917c3f483e9f2cc22ed7dd06812d561b0/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The postint script doesn't enable the systemd service on install, which
leads at least inexperienced systemd users like myself to spend a lot of
time trying to work out why shorewall doesn't start at boot. I'm pretty
sure all the other packages I installed (e.g. apache2,
Public bug reported:
$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of
After updating to the latest packages, this issue is solve. I can lxc-
start, lxc-attach, lxc-stop, and lxc-execute.
I do get some warning/error spew when running lxc-execute though. If
this looks unexpected, I can open a separate bug for it:
$ lxc-execute -n t1 -- /bin/bash
lxc-execute:
After updating to the latest packages, this issue is solve. I can lxc-
start, lxc-attach, lxc-stop, and lxc-execute.
I do get some warning/error spew when running lxc-execute though. If
this looks unexpected, I can open a separate bug for it:
$ lxc-execute -n t1 -- /bin/bash
lxc-execute:
The same issue happens when running:
gdb --args wish /usr/bin/gitk -- -n 100
(or just "gitk -n 100" if not running under gdb)
The same issue repros when closing the window in the following ways:
- Clicking the close "x" icon on the window title bar
- Selecting close from the window's menu (in
Public bug reported:
When the user closes the window that wish displays (e.g. types CTRL+F4
in XFCE), wish experiences a segfault. This can be reproduced either by
simply running "wish", or by running a wish-based application such as
gitk.
$ gdb wish
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright
Thanks. The chown solves the issue. I didn't need to make the
modification to the pam config file at all. I do need to do the chown
every time I log in though, with or without the pam change.
FWIW, when I ssh into the working server, the relevant /sys directory is
owned by swarren:swarren without
Thanks. The chown solves the issue. I didn't need to make the
modification to the pam config file at all. I do need to do the chown
every time I log in though, with or without the pam change.
FWIW, when I ssh into the working server, the relevant /sys directory is
owned by swarren:swarren without
Could you please expand on "Then re-chown your current systemd cgroup"?
I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
path I should chown.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Could you please expand on "Then re-chown your current systemd cgroup"?
I'm not sure exactly how/where cgroups get mounted, so I'm not sure what
path I should chown.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Yes, I'm running lightdm.
$ cat /etc/pam.d/common-session
session [default=1] pam_permit.so
session requisite pam_deny.so
session requiredpam_permit.so
session optionalpam_umask.so
session required
Yes, I'm running lightdm.
$ cat /etc/pam.d/common-session
session [default=1] pam_permit.so
session requisite pam_deny.so
session requiredpam_permit.so
session optionalpam_umask.so
session required
Switching the linode system to the Ubuntu kernel (booted via pv-grub)
didn't make that system fail. Perhaps the difference is cgroup setup via
ssh vs XFCE/GUI login?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
Switching the linode system to the Ubuntu kernel (booted via pv-grub)
didn't make that system fail. Perhaps the difference is cgroup setup via
ssh vs XFCE/GUI login?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes
ago. The failing system is a laptop running XFCE GUI, and I'm attempting
to use LXC from a GUI terminal. The other system is a linode that I
access via ssh, and LXC works fine there. I believe I've configured the
two systems
I have 2 Xenial systems. They are both fully up-to-date as of 5 minutes
ago. The failing system is a laptop running XFCE GUI, and I'm attempting
to use LXC from a GUI terminal. The other system is a linode that I
access via ssh, and LXC works fine there. I believe I've configured the
two systems
Public bug reported:
On Ubuntu Xenial pre-release, I see the following, so can't start a
container:
[swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu container (release=trusty,
Public bug reported:
On Ubuntu Xenial pre-release, I see the following, so can't start a
container:
[swarren@sprint ~]$ lxc-create -t download -n t2 -- -d ubuntu -r trusty -a amd64
Using image from local cache
Unpacking the rootfs
---
You just created an Ubuntu container (release=trusty,
Bug 4875 reports basically the exact same issue. It is marked as a
duplicated of bug 4695. Should this bug be marked as a duplicate too?
However, bug 4695 is more about the handling of multiple entries in the
keyboard shortcut config files with the same logical function not being
ideal. This bug
This also affects Lucid, and I would guess Precise. I can't quite tell
how to add extra releases in to the list above.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to spamassassin in Ubuntu.
https://bugs.launchpad.net/bugs/1397706
This also affects Lucid, and I would guess Precise. I can't quite tell
how to add extra releases in to the list above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397706
Title:
Argument
Re: comment #16: In Trusty/14.04, removing overlay-scrollbar does not
solve the issue. I never tested if it worked for me on earlier releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048805
I installed indicator-sound-gtk2_12.10.0.1-0ubuntu2.3_amd64.deb, and it
fixed the issue for me. Is there a good place to indicate test results
for proposed packages?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Dmitrijs, any chance of an SRU for Quantal/Raring/... so people don't
have to upgrade to a not-yet-released OS to get the new package?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1194183
Title:
Public bug reported:
dtc v1.4.0 has been tagged/released at
git://git.jdl.com/software/dtc.git. It'd be great if this could be
packaged up, and back-ported into as many Ubuntu versions as possible
(at least 10.04, 12.04, and any currently supported regular releases
would be awesome).
This
** Bug watch added: Debian Bug tracker #713991
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713991
** Also affects: device-tree-compiler (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713991
Importance: Unknown
Status: Unknown
--
You received this bug
** Bug watch added: Gentoo Bugzilla #474620
https://bugs.gentoo.org/show_bug.cgi?id=474620
** Also affects: device-tree-compiler (Gentoo Linux) via
https://bugs.gentoo.org/show_bug.cgi?id=474620
Importance: Unknown
Status: Unknown
** Bug watch added: Novell/SUSE Bugzilla #826457
Yes, I can confirm this is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1165614
Title:
gcc-4.7 crashes compiling kernel 3.8 for ARM on ARM
To manage notifications about this bug go to:
Public bug reported:
Running Ubuntu 13.04 on the ARM Chromebook:
$ gcc --version
gcc (Ubuntu/Linaro 4.7.2-23ubuntu1) 4.7.3
Set up:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git checkout v3.8
make tegra_defconfig
Multiple crashes/ICE show up when
Strange. I believe the file /etc/xdg/xfce4/xfconf/xfce-perchannel-
xml/xfce4-keyboard-shortcuts.xml is the default content for
.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml,
and should be copied to it when Reset to defaults is executed in the
XFCE settings application.
This is reported in the XFCE bug-tracker as at least:
https://bugzilla.xfce.org/show_bug.cgi?id=4875
https://bugzilla.xfce.org/show_bug.cgi?id=7070
The first of those is marked a duplicate of:
https://bugzilla.xfce.org/show_bug.cgi?id=4695
although I'm not entirely convinced that it really is a
The comments in https://bugs.kde.org/show_bug.cgi?id=152030 imply that
the end-user is free to simply use/install a different theme which
actually does honor the active/inactive color settings. However, it
doesn't seem like any of the 9 schemes that ship with Ubuntu 12.10
actually do honor those
At least for RAID-1, and I assume probably for other RAID levels, using
--assume-clean when creating the arrays would be an extremely bad idea.
The md feature to check whether the two mirrors of the array are still
identical would fail horribly if they never started out being identical.
--
You
Editing /etc/default/dropbear doesn't seem to affect the initramfs at
all in Quantal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904045
Title:
Dropbear init script doesn't support multiple ports
Public bug reported:
I have a server with a static IP, so I put the following into
/etc/network/interfaces to configure it:
auto eth0
iface eth0 inet static
address 192.168.63.152
network 192.168.63.0
netmask 255.255.255.0
broadcast 192.168.63.255
gateway 192.168.63.1
Public bug reported:
I'm running Quantal, with the following HW:
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS880 Host Bridge
...
01:05.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS880
[Radeon HD 4290]
When I boot, I see the BIOS screen, then grub (I've commented
A solution to making this work remotely is:
1) SSH in
2) Manually run cryptsetup; basically run ps, find the cryptsetup command-line,
remote the key-file option, run it, type the password into cryptsetup
3) kill cryptsept process, kill plymouth process
It just worked for me:-)
--
You received
I don't think that last bug edit is valid; the bug is in Flash's use of
the VDPAU API, and hence it is related to libvdpau acceleration not
video acceleration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The whole point of the libvdpau patch is that it is easily reversible,
and integrates trivially with the Ubuntu packaging process.
To reverse it, just change the configuration file.
To integrate with the packaging process, put the config file in the
Flash package. That way, if a new Flash
The following libvdpau patch detects Flash and implements some
workarounds:
http://lists.freedesktop.org/archives/vdpau/2012-May/22.html
I'm not entirely sure if it's appropriate to add this to libvdpau, but
it certainly does solve the issues on my machine...
--
You received this bug
If hibernate must be disabled by default (which IMHO is a silly idea,
since it makes the whole fact that hibernate even exists completely
undiscoverable), then rather than directing users to create a file in
/etc (hardly something that the average end-user is going to know how to
do), why not
Jan, this definitely isn't a libvdpau problem; libvdpau is just a
wrapper library that is used to locate the vendor-specific VDPAU driver.
The problem is either in the Ubuntu desktop environment (window
manager/compositor), the application which uses VDPAU (e.g. Adobe Flash)
or the VDPAU driver
Ah right, I thought that by blue you meant a solid single color,
rather than just swapped chroma components. In that case, yes, as you
say, I believe Pierre-Loup has confirmed this is a bug in Adobe Flash,
hence the workaround he created.
--
You received this bug notification because you are a
It doesn't just work. Just work means it works without having to
change anything to make it work.
The reason I filed this bug is not because it can't be made to work, but
that the default configuration of the two packages (postfix, spamass-
milter IIRC) when simply apt-get install'd is such that
Will there be an update released for Natty?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/771905
Title:
(natty/nvidia) No logo at boot on nvidia card
To manage notifications about this bug go to:
Psychotron's workaround of adding GRUB_GFXPAYLOAD_LINUX=text to
/etc/defaults/grub works for me.
Alternatively, another option that works for me: Find the following pre-
existing text in /etc/defaults/grub:
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
and
If you break into the grub menu, edit the grub option you want to boot,
and remote quiet splash from the linux command-line, you'll boot into
text mode, and hence see the crypt password prompt.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I believe the syntax in the /etc/sudoers file is #includedir
/etc/sudoers.d not includedir /etc/sudoers.d, i.e. you do need the
leading # character; the visudo syntax error message when you omit it is
correct. See `man sudoers`.
--
You received this bug notification because you are a member of
Hmm. I partially take that back. The actual content of the kernel
command-line isn't important. What is important is editing in grub (i.e.
at the grub menu, press e to edit, don't make any changes, then press
ctrl-x to boot). That works most of the time, but just occasionally
doesn't.
--
You
If you edit /boot/grub.cfg and override the timeout lines to be
timeout=0, grub never displays a boot menu, but instead jumps straight
to booting the default option. In this case, the password prompt is
visible for me.
IIRC, by default, Ubuntu configures grub to *not* display the menu
(hence this
Me too.
Is this related to using a video/X driver that doesn't support KMS? I
notice that Jerico's lspci.txt in comment #5 shows an ATI graphics card,
and the fglrx binary driver is listed in ProcModules.txt in comment #8.
(As background, in Maverick, I uninstalled the Ubuntu NVIDIA driver
One proposal from OEM is to keep hibernate enabled at the kernel
level, retain an option in gnome-power-manager to put the system
into hibernate on a critical battery event, and remove hibernate from
the rest of the UI (the power menu + shutdown dialog).
That doesn't make a lot of sense to
Public bug reported:
I'm running xvnc4viewer on Ubuntu to connect to a Windows 7 VM inside
qemu-kvm running under Lucid 64.
When I connect from the Lucid machine to the VM running locally,
CTRL-C/V for cut/paste work, as do many other keyboard shortcuts using
the CTRL modifier. IIRC, I also ran
** Description changed:
I'm running xvnc4viewer on Ubuntu to connect to a Windows 7 VM inside
qemu-kvm running under Lucid 64.
When I connect from the Lucid machine to the VM running locally,
CTRL-C/V for cut/paste work, as do many other keyboard shortcuts using
- the CTRL modifier.
+
Public bug reported:
I'm connecting from a Maverick client to a Windows 7 VM (inside qemu-
kvm) running on Lucid.
If I connect using xvnc4viewer (and run a utility called autocutsel to
sync X's various selection/cut buffers), then I can copy from the VM
inside the VNC viewer, and paste into
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/702750
Title:
gvncviewer doesn't implement cut/paste buffer sharing/syncing
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Tags removed: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695249
Title:
ASUS G73JW fails to suspend or
I've found the complete solution!
It's at http://ubuntuforums.org/archive/index.php/t-1444822.html, in
John Dias's April 27th, 2010, 02:16 AM comment. Just in case that goes
away, and in the hope of bumping the information in Google's ranking
(that link is on something like page 6 of my Google
I noticed there was a new BIOS, so I upgraded (old version: 202 new
version: 203).
I don't see any difference in behaviour; to recap, with USB ports
enabled, suspend fails since it can't suspend the usb3 device, with USB
ports disabled, suspend just hangs and the machine locks up (no kernel
andy1, your issue sounds unrelated to this bug. You might have
better luck with speaker-test (e.g. perhaps only have to run it once
rather than N times), since I assume Front_Left.wav is a very short
sample?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Device usb3 in the kernel error log is the USB3 bus controller/root-hub;
lsusb -t lists it as XHCI instead of EHCI. If I disable this port in
the BIOS (security option, USB ports, lock external ports), the USB3
bus no longer shows up in lsusb, and suspend is not aborted with the
kernel messages
In fact, both 2.6.35-24.42 and 2.6.37-020637rc2.201011160905 hang in the
same way with USB ports disabled,as described above.
I tried netconsole, and I get no kind of error messages at all during
suspend from either kernel; just expected messages e.g. wireless
shutting down etc.
--
You received
With 2.6.35-24.42:
Following https://wiki.ubuntu.com/DebuggingKernelSuspend (i.e. echo 1
/sys/power/pm_trace), the CMOS time doesn't seem to be reset to a debug
value upon boot after hang/power-cycle (the time is still exactly
correct), so I think any hash matches message is invalid. I think
Public bug reported:
Attempts to either suspend or hibernate my new laptop, it will fail. The
system is still running OK and dumped back to X with the
screensaver/lock running.
The following messages are in /var/log/syslog:
Dec 28 20:59:03 dart kernel: [ 125.572258] PM: Syncing filesystems ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695249
Title:
ASUS G73JW fails to suspend or hibernate: pm_op(): usb_dev_suspend+0x0/0x20
returns -2
--
ubuntu-bugs mailing list
I also tried the most recent mainline kernel I could find in the PPA,
linux-
image-2.6.37-020637rc2-generic_2.6.37-020637rc2.201011160905_amd64.deb.
With that kernel, either suspend or hibernate simply hang with a blank
screen with the cursor flashing, and require a hard power cycle.
** Tags
Yup, fixes the issue in ddd too (see dup bug 574157 comment #1). Thanks!
--
mouse trapped in box for Open Motif
https://bugs.launchpad.net/bugs/553415
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
1 - 100 of 335 matches
Mail list logo
