After weeks of work preparing some historical Fortran code came to the
Fort77 to start compiling it. Compiles fine but have exactly the bug as
described above. However after a quick google could not even locate the
source code for the libf2c. Could somebody please post the link to the
sources. I
Public bug reported:
I was using UbuntuStudio 23.10 with no issues. When I updated to 24.04,
on my first boot of the new OS, the system hung with a black screen just
before the login screen. I completely deleted the original image,
reinstalled UbuntuStudio 24.04, and tried again. It worked until
Confirmed on Linx 1010b on LinuxMint 20.3
Added options snd-intel-dspcfg dsp_driver=2 to /etc/modprobe.d/alsa-base.conf
reboot into 5.13
spd-say "Talking too slowly"
shut down
go to bios and save
reboot into 5.13
spd-say "That'll do nicely"
Works in 5.14, plus it seems to still be good in 5.11.
FWIW:
dmesg | grep -Pi "alsa|pulse|sound|audio"
... for 5.11 and 5.14 differ.
5.11.0-46-generic (works)
[0.136592] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio)
[3.051445] i915 :00:02.0: [drm] HDaudio controller not detected, using
LPE audio instead
[ 10.791703] input: Intel HDMI/DP
Same thing for me: Dell XPS 13 with QCA6174 wlan card
It often crashes after the laptop suspend
No porblem if I manually switch off the wlan before suspending.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've installed 21.10 on a stick and updated the kernel to 5.12.0-27. It
works fine there, so this is probably about kernel >= 5.13 AND NOT dist
=21.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I live-booted from U 21.10*, which has a 5.13.0-19 kernel.
Bafflingly, sound test worked from the live system, even though alsa-
info shows rt5640,sof-bytcht.
Late now. I'll do it again tomorrow and grab inxi/pactl/alsa-info.
*Lost time making a USB boot stick with 32 bit EFI capability. mkusb
Public bug reported:
Using the built in speakers on a Linx 1010b. The 5.11 kernel works fine,
but 5.13 and 5.14 fail.
The card, when working is seen in alsa-info as bytcrrt5640,bytcr-rt5640,
whereas in the later (hwe-20.04-edge, oem-20.04d) kernels where it
fails, it is seen as
Hello,
I have the same issues on a fleet on Ubuntu 20.04 machines joined to a
Univention Corporate Server domain. UCS uses Samba4 as a background.
Is there any security concern about the 'ad_gpo_access_control =
permissive' or 'access_provider = permit' in sssd.conf?
Thank you for looking into
Like Hugo Ferreira, switching to the NVIDIA Server Driver instead of the
classic NVIDIA driver finally did the job. Everything I tried before didn't
work.
So it is finally fixed for me, although I don't know if there are any drawbacks
to using the Server driver :)
--
You received this bug
Disk full today! Same error messages
syslog.* files about 30-40GB
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908429
Title:
gnome-shell fills syslog: Attempting to run a JS callback during
My CI/CD now works properly since this morning (see #48).
And it's using the same base image (bento/ubuntu-20.04 202008.16.0) so there is
indeed a working fix on the apt servers side.
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Occurs to me in a daily CI/CD vagrant build since Sep 23, 2020 3:30 AM:
default: Processing triggers for libc-bin (2.31-0ubuntu9) ...
default: E
default: :
default: Could not configure 'libc6:i386'.
default: E
default: :
default: Could not perform immediate
** Attachment added: "Full "vagrant up" log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1871268/+attachment/5414080/+files/vagrant.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is there any update or workaround on this issue? This is going to be a
problem to everyone in enterprise environments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714244
Title:
[snap] apparmor
These checks break programs compiled with _FORTIFY_SOURCE that allocate
fd_sets on the heap. This has long been supported by Linux, all BSDs and
many commercial Unix as a way to avoid FD_SETSIZE limits.
Please consider revising the checks to detect explicitly allocated
fd_sets or add a
This was resolved by removing Mono from my system
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883847
Title:
Upgrade from 18.04 to 20.04 failed
To manage notifications about this bug go to:
Public bug reported:
Calculating the changes
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This was caused by:
* Upgrading to a pre-release version of Ubuntu
This is most likely a transient problem,
please try again later.
If none of this
*** This bug is a duplicate of bug 1875062 ***
https://bugs.launchpad.net/bugs/1875062
Maybe duplicate of
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062 ?
** This bug has been marked a duplicate of bug 1875062
[20.04] Keyboard layout not enabled immediately during
*** This bug is a duplicate of bug 1875062 ***
https://bugs.launchpad.net/bugs/1875062
Got the same problem with Ubuntu 20.04 installer ; Ubiquity doesn't use
selected keyboard layout on account creation, it always turn to QWERTY
(I select AZERTY on localization options)
--
You received
** Also affects: kitty (Arch Linux)
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/1844854
Title:
Powerline symbol rendering
To manage notifications
Yep, confirmed here too...
Running up a couple of new nodes, and was losing my mind trying to
figure out what I was doing wrong. Went back to an existing node to
confirm our rollout docs were correct, and config was correct, only
thing I could find was existing servers were running
Public bug reported:
I am installing Ubuntu 19.10 on my new computer, keeping Windows 10 as
dual-boot. I've previously disabled secure-boot and settled legagy boot instead
of UEFI.
I've manually partitioned my free disk space with LVM and an EXT4 root
partition. At the end of the installation
I confirm the issue is still here (Ubuntu Server 18.04.3), as the
package has not been updated (6.4.0+dfsg-1).
Backporting version 6.6.0+dfsg-1build1 from Cosmic fixes the issue, but
since this package depends on libc6 it may not be a good solution for
every setup.
--
You received this bug
Hello,
As RussianNeuroMancer, my explorer finally starts after almost one hour.
But i'm not on virutal machine, it's happening on my laptop under 19.04.
We are 4 working with same settings and i'm the only one experiencing this
issue..
--
You received this bug notification because you are a
kernel 5.0.0-21-generic fixes the issue. Thanks for your help!
** Tags removed: disco verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I obviously can't run apport-collect after a kernel panic, but will be
more than happy to upload any log file that could help troubleshooting.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "lspci-vvnn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829652/+attachment/5264783/+files/lspci-vvnn.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829652
Public bug reported:
Hi,
I've recently upgraded my system to ubuntu 19.04, and kernel consistently
panics when I boot a virtual machine using an SR-IOV VFIO virtual function.
Could reproduce with 5.0.0-13-generic and 5.0.0-15-generic, doesn't happen with
4.18.0-20-generic.
I'm using libvirt
** Attachment added: "Panic stack trace"
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1829652/+attachment/5264773/+files/panic_stack_trace.txt
** Description changed:
Hi,
I've recently upgraded my system to ubuntu 19.04, and kernel consistently
panics when I boot a
https://www.oracle.com/technetwork/java/java-se-support-roadmap.html
Oracle will no longer provide free public updates for commercial users
of Java 8 after January 2019 (i.e. this month). As such, Java users will
need to upgrade their JDK very soon, so I think this bug is more urgent
now.
--
Public bug reported:
Upgrading from 16.04 to 18.04
Unsigned kernel:
Cannot upgrade Secure Boot enforcement policy due to unsigned kernel:
Your system has UEFI Secure Boot enabled in firmware, and the following
kernels present on your system are unsigned:
4.4.0-134-generic
These kernels
Public bug reported:
I was installing Ubuntu, then something like a missing grub file
appeared. Then the installation closed
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu
Hi,
I'm using the same MSI and I have the same problem. My touchpad doesn't
work when the acpi=off is in the Grub but I can't boot without this
parameter. Without that, my cpu is stuck!
More than 1 years after, is there a standard solution?
BR
--
You received this bug notification because you
It looks like the same issue occurs on Intel Core 2 Duo CPU P9400 @
2.40Ghz with i686 Xubuntu with Kernel linux-image-4.13.0-32-generic.
It loops directly after grub before any kernel print out back to bios.
It boots with the previous kernel 4.10.0-42-generic.
--
You received this bug
I retried this morning, and problem solved!
Thanks
** Changed in: linux-azure (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745169
Title:
Kernel
Jan 24 12:12:55 es-usb kernel: Code: Bad RIP value.
> Jan 24 12:12:55 es-usb kernel: RIP: 0x7f7d7d67e7a0 RSP: b490c5aa3f50
> Jan 24 12:12:55 es-usb kernel: CR2: 7f7d7d67e7a0
> Jan 24 12:12:55 es-usb kernel: ---[ end trace 3100a53c6de7c0c4 ]---
>
> Tha
.
Jan 24 12:12:55 es-usb kernel: RIP: 0x7f7d7d67e7a0 RSP: b490c5aa3f50
Jan 24 12:12:55 es-usb kernel: CR2: 7f7d7d67e7a0
Jan 24 12:12:55 es-usb kernel: ---[ end trace 3100a53c6de7c0c4 ]---
Thanks for your help
Damien
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status
over 1 year after last comment... behavior still exists.
ash@CASE:~$ uname -a
Linux CASE 4.13.0-21-generic #24-Ubuntu SMP Mon Dec 18 17:29:16 UTC 2017 x86_64
x86_64 x86_64 GNU/Linux
ash@CASE:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
*** This bug is a duplicate of bug 1732515 ***
https://bugs.launchpad.net/bugs/1732515
Public bug reported:
Not sure what the issue is. I simply ran "sudo apt-get upgrade" and it output
that
"Errors were encountered while processing:
grub-efi-amd64-signed
shim-signed"
Hope this helps!
Of course and I've installed them on my main machine but that was an
upgrade over SSH and the term info were not on that remote host. All in
all, I think it was more my fault than anything else...
Maybe, to avoid this pitfall for other users, 'xterm' could be assumed
if the TERM variable is not
I eventually succeeded to finish upgrading the system. The only thing I
had to manually fix was to set TERM=xterm because the installer was not
able to pop-up the purple selection screen with my self-compiled st
terminal.
Do not know if this is related to this automatically generated bug
report
Public bug reported:
Was just trying to upgrade from 14.04 to 16.04 and the installer
reported that issue and asked me to fill this...
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.8
ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17
The bug is Ubuntu 16.04 - grub-efi-amd64-signed failed to install into
/target/ Despite Phillip Susi suggestion to partition the disk using
GPT and set up an EFI system partition to install in EFI mode. This will
be done for you if you choose the "use entire disk" guided install
option.
THIS
Hi,
Same issue here (ubuntu 16.10 x64) on a Lenovo x1 Carbon.
my xinput list:
⎡ Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)]
⎜ ↳ ELAN Touchscreen id=11 [slave
Please read the bug description. I installed muon and that did not solve the
problem.
Related bug: https://bugs.kde.org/show_bug.cgi?id=376241 (note that this
affects many users).
** Bug watch added: KDE Bug Tracking System #376241
https://bugs.kde.org/show_bug.cgi?id=376241
--
You
ff: Categories: ("Plasma Comic")
knewstuff: Using registry file:
"/home/damien/.local/share/knewstuff3/.knsregistry"
knewstuff: Loading KNS2 registry of files for the component: ""
knewstuff: Cache read... entries: 0
knewstuff: loading providers from "http://do
For the record, I'm having this problem, even if my file won't go too
big to crash my system, because I logout everyday.
I'm using 16.04 (LTS) with 'lightdm' and 'awesome' window manager, so no
gdm here.
For me, it seems it's firefox plugin container of adobe's flashplayer
which is dropping tons
Public bug reported:
1/ ubuntu 14.04.5 LTS
release 14.04
2/ package version:
ubuntu@ubuntu:/$ sudo apt-cache policy pkgname
N: Unable to locate package pkgname
ubuntu@ubuntu:/$ 1473366353536 addons.update-checker WARNUpdate manifest
for e10sroll...@mozilla.org did not contain an
This bug is also present in 14.04. With my minified css file, what i
searched for was irrelevant, it always resulted in Gedit crashing with
SIGSEGV gtk_iter_forward_to_tag_toggle() Renaming the file to .html from
.css gedit no longer crashed.
--
You received this bug notification because you are
The problem is solved if installing the packet ubuntu-sdk-
api-15.04-armhf before launching the SDK. Maybe something should state
the packet dependency before a new kit for armhf target is created (or
at the beginning of the kit creation)
--
You received this bug notification because you are a
Pilot6 : Ok ! Thank you for your patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542944
Title:
QCA9565 / AR9565 bluetooth not work
To manage notifications about this bug go to:
Any news on 14.04 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/953875
Title:
Encrypted swap no longer mounted at bootup
To manage notifications about this bug go to:
Sorry but I don't understand
What is the difference :
- verification-needed-trusty
- verification-needed-vivid
- verification-needed-wily
- verification-needed-xenial
I have 14.04 (trusty ?) and I Have installed prposed kernel 4.2.0-36 and It's
work.
Can I test kernel for others ubuntu
tags: added: verification-done-trusty
removed: verification-needed-trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542944
Title:
QCA9565 / AR9565 bluetooth not work
To manage notifications
For me, the wifi and the bluetooth work at the same time...
My laptop is connected in wifi and I can listen a webradio to my
bluetooth hifi receiver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok.
I have installed manually 4.2.0-36 and blutooth work fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542944
Title:
QCA9565 / AR9565 bluetooth not work
To manage notifications about this
*** This bug is a duplicate of bug 1380702 ***
https://bugs.launchpad.net/bugs/1380702
I also confirm that the issue is solved by removing the appmenu-qt5 app.
BUT Texmaker windows are horrible.
SO: Ubuntu 16.04
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have tried :
install "old" generic-lts-trusty (3.13), reboot and select the old
kernel in grub. After the system booted, Launch update. but message says
me that packages are up to date.
What I need to do ?
thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Yes !
You have says me by mail the february 6 2016 :
"But it will be much more convenient if you upgrade your kernel first by
running
sudo apt-get install linux-generic-lts-wily
and reboot."
How I need to do ? The old 3.19 kernel was removed because my boot
partition is too small.
--
You
Hi,
I have enabled the the proposed in update manager and make an update. Then I
have removed the btusb patch sended by Pilot6.
Now, a uname - a return : 4.2.0-27-generic #32~14.04.1-Ubuntu SMP Fri
Jan 22 15:32:26 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
an apt-get upgrade -s return 0 package to
Also affects Sony Vaio SVS15 series laptop. Hibernate or suspend no
change in max fan speed. No PWM capability.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1565864
Title:
Hardware-specific: Fan
Great ! It work !
Thank you !
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542944
Title:
QCA9565 / AR9565 bluetooth not work
To manage notifications about this bug go to:
Thanks !
I will test it shortly !
Le 08/02/2016 10:42, Pilot6 a écrit :
> I built a test module. You can install it by running terminal commands:
>
> wget
> https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542944-dkms_0.1_all.deb
> sudo dpkg -i
Hi.
There is an error when enter the sudo dpkg -i btusb-
lp1542944-dkms_0.1_all.deb command :
Sélection du paquet btusb-lp1542944-dkms précédemment désélectionné.
(Lecture de la base de données... 261857 fichiers et répertoires déjà
installés.)
Préparation du décompactage de
to do ?
thanks.
Damien
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1542944
Title:
QCA9565 / AR9565 bluetooth not work
To manage notifications about this bug go to:
https://bugs.launchpad.net
You will find the output of dmesg as attached file.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1542944/+attachment/4567339/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
You will find the output of lsusb as attached file.
** Attachment added: "lsusb.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1542944/+attachment/4567338/+files/lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
You will find the output of lspci as attached file.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-lts-wily/+bug/1542944/+attachment/4567337/+files/lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
usb-devices | awk '/e095/' RS=
T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=02 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdID=e095 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon)
I used a MicroSDHC with a MicroSD - SD adapter. The card itself is
chinese, brand Xedain. If that matters. I didn't think it would be
important, but I can try with other cards (SDHC, MicroSD, MIcroSDHC) and
brands (real ADATA, Sandisk, Patriot)
It's unfortunate to have to reverse engineer a
Hi Olerem,
Thanks for the prompt answer. Unforutnatley, that NULL pointer didn't seem to
help much.
The computer boots and the driver loads, but when I insert a SD-card, the
laptop freezes after about 8-10 seconds. Just enough time to take a picture of
the dmesg:
My laptop is a TOSHIBA Satellite L40-D and I'm having the same issue
with the Alcor Card Reader
$ lspci
Unassigned class [ff00]: Device [1aea:6601]
This is running Ubuntu 15.04 on 3.19.0-47
Cards inserted never even get detected by the system. I see no log entry or
error in dmesg.
--
You
I'm having the same issue with the Alcor Card Reader
$ lspci
Unassigned class [ff00]: Device [1aea:6601]
This is running Ubuntu 15.04 on 3.19.0-47
Cards inserted never even get detected by the system. I see no log entry or
error in dmesg.
--
You received this bug notification because you are
There's also a similar error for
_cairo_path_fixed_approximate_stroke_extents():
cairo-gl-msaa-compositor.c:584:6: error: too few arguments to function
‘_cairo_path_fixed_approximate_stroke_extents’
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It seems the GL backend still doesn't compile as a couple uses of
_cairo_surface_init weren't updated:
cairo-gl-source.c:76:5: error: too few arguments to function
‘_cairo_surface_init’
cairo-gl-source.c:103:5: error: too few arguments to function
‘_cairo_surface_init’
--
You received this
*** This bug is a duplicate of bug 344878 ***
https://bugs.launchpad.net/bugs/344878
Try to long path tool. It is very helpful.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/592303
Title:
*** This bug is a duplicate of bug 344878 ***
https://bugs.launchpad.net/bugs/344878
Try to long path tool. It is very helpful.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
Hi
Well it doesn't seem to hang anymore under debian jessie
I guess I will not find a way to make it work while it seems that there's no
driver for this printer
sorry for the noise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
error
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libjpeg62:amd64 6b1-4ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
Date: Sat Feb 7 09:08:47
** Description changed:
hi all,
Base informations :
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
# uname -a
Linux school 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16
** Description changed:
hi all,
Base informations :
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
# uname -a
Linux school 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16
** Description changed:
hi all,
- Base informations :
+ Base informations :
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.1 LTS
Release: 14.04
Codename: trusty
# uname -a
Linux school 3.13.0-44-generic
Public bug reported:
hi all,
Base informations :
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.1 LTS
Release:14.04
Codename: trusty
# uname -a
Linux school 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43 UTC 2014
x86_64
additionnal stack traces, not exactly the same as the OP ones.
Jan 21 06:05:20 filer2 kernel: [398213.798328] INFO: task nfsd:1440 blocked for
more than 120 seconds.
Jan 21 06:05:20 filer2 kernel: [398213.798371] Not tainted
3.13.0-24-generic #47-Ubuntu
Jan 21 06:05:20 filer2 kernel:
I forgot to notice that this happens for me on :
Linux daminetreg-laptop 3.13.0-44-generic #73-Ubuntu SMP Tue Dec 16 00:22:43
UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
for Ubuntu 14.04.1 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've the issue also on a MacBookPro 11,1. It takes exactly 34,2 seconds
for the system to wakeup.
Strangely dmesg says the wakeup started on second 1864 and ended on 1869
:
[ 1864.618554] smpboot: CPU 7 is now offline
[ 1864.636283] ACPI: Low-level resume complete
[ 1864.636333] PM: Restoring
Same issue for us too on a production environment using Ubuntu Server
14.04.
nsf3 Workaround is confirmed to work ? what are we loosing from using
nfs4 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Version 3.5 just made its way into Debian repos. Can we get this into
Trusty?
Regards,
** Affects: zam-plugins (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This has seemed to resolve itself with later kernel packages. I no
longer have any resume issues, with either mainline kernel or normal
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349225
Public bug reported:
Having trouble resuming from suspend. The whole system hangs upon
resume. No mouse, no keyboard input.
ProblemType: KernelOops
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-5-generic 3.16.0-5.10
ProcVersionSignature: Ubuntu 3.16.0-5.10-generic 3.16.0-rc6
Uname:
I am also having this issue in Ubuntu 14.04 and my Lenovo IdeaPad Flex
15 (59387556).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1264384
Title:
8086:08b2 [Lenovo ThinkPad S3-S440] Wireless
I'm not really sure the problem I managed to reproduced on v3.15-rc2 is
the exact same. The symptoms are the same: I can't resume from suspend.
Still, as I don't have sound on v3.15-rc2, I don't think the problems
are related. Please advise on what I can do to help get this bug(s)
fixed.
--
You
I have a hard time reproducing again. The problem is twofold:
1. the suspend/resume problem does not always happen
2. this kernel does neither have sound nor wifi which makes it inconvenient to
set as my default kernel
Do you think I could configure wifi and sound on the 3.15rc2 kernel?
--
Public bug reported:
Here are some details as asked in bug #1305371
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
NonfreeKernelModules: wl
Suspend/resume was working fine in 13.10 on the same hardware.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1328801
Title:
pacmd list failed suspend resume
To manage notifications about this bug
Using v3.15-rc2-trusty (3.15.0-031500rc2-generic #201404201435 SMP), I *managed
to reproduce* the suspend/resume problem.
Using this kernel, the wifi is not working: this is problematic because I can't
just report bugs using apport from there. Nevertheless, when the problem
occured again in
Please find attached the /proc/acpi/wakeup while in v3.15-rc2-trusty. I
didn't follow the resume-trace debugging procedure as it looks like it
is related to debugging resume while I think my problem is on suspend:
when I close the lid and the light does not blink, I know the computer
won't resume.
I have a similar problem on the exact same architecture. Nevertheless, I
don't think my problem depends on how long the computer stays suspended.
From what I can see, as soon as I close the lid I know if resume will
work fine or not:
- if the suspend light starts blinking after a few seconds, the
*** This bug is a duplicate of bug 1297961 ***
https://bugs.launchpad.net/bugs/1297961
** Changed in: linux (Ubuntu)
Status: Expired = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1 - 100 of 873 matches
Mail list logo
