Vyron, how did you revert?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882991
Title:
Kernel 5.4.0-37-generic leads to black screen after grub,
5.4.0-26-generic works normally
Stat
I posted that before I was done putting relevant information in.
I have a Lenovo P51 running Kubuntu 20.04 that I just updated to
5.4.0-37 and am getting a black screen after rebooting. I was/am running
Nvidia driver 440.82 and saw the DKMS process during the apt upgrade.
I tried resigning the dr
** Changed in: linux (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882991
Title:
Kernel 5.4.0-37-generic leads to black screen after grub,
Vyron, thanks for the response.
I was able go to TTY2 (CTL-ALT-F2) and get the dpkg log from when I ran
`upgrade -y`; it is attached here. Not sure what else to look at or how
to TS from here.
** Attachment added: "list of upgraded packages with with 5.4.0-37 kernel"
https://bugs.launchpad.n
I ran `apport-bug` and copied it off to an SMB share, but am not sure
it's propert etiquette, or wise, to attach publicly.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1882991
Title:
K
I can boot fine to either kernel (5.4.0.33 or .37) if nvidia driver is
not installed, using nouveau. But no matter what Nvidia driver I use (or
install method) I cannot get the NVidia driver reinstalled properly.
--
You received this bug notification because you are a member of Kernel
Packages, w
At some point I was able to purge anything installed with *nvidia* in
it... reboot and get UI without `nomodeset` intervention. I then
installed `nvidia-driver-435` and have left it alone since then. I'll
try 440 again another time.
--
You received this bug notification because you are a member o
Well "another time" came and I installed 440 again via apt and its
booting fine; can only assume that the blanket purge of all things
nvidia and subsequent reboots was the resolution.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux i
I just encountered this as well with an identical drive and ID.
[1342096.266871] usb 2-1.2: new high-speed USB device number 21 using ehci-pci
[1342096.361163] usb 2-1.2: New USB device found, idVendor=0781, idProduct=5581
[1342096.361174] usb 2-1.2: New USB device strings: Mfr=1, Product=2,
Seria
Same issue here. Ubuntu Gnome 16.04, Lenovo y40.
Running on kernel 4.2.0 or disabling my discrete gpu (AMD) fixes it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1574125
Title:
suspe
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
[sudo] password for derek:
A08
08/31/2015
- There was no improvement in the symptoms. The external monitors still
fail to wake.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You receiv
$ cat /proc/version
Linux version 4.4.0-040400rc8-generic (kernel@gloin) (gcc version 5.2.1
20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201601051225 SMP Tue Jan 5 17:27:39 UTC
2016
Bug still exists. No messages appear in any of dmesg faillog kern.log
syslog Xorg.0.log
** Changed in: linux (Ubuntu)
the drm-intel-nightly kernel didn't fix the issue.
I began attempting to trace the issue and search for clues as to why
this is happening.
I am attaching three kernel log files with kernel switch: drm.debug=0x05
All of these are kernel logs after a "xset dpms force off".
- "success" is with the
Additional info: When in intended setup (two monitors on one DP) the
ASUS brand monitor flickers occasionally (not a nuisance)
- Connecting just the ASUS to the adapter (other HDMI port unpopulated) the
monitor flickers repeatedly, indefinitely, often. This is regardless of which
of the 2 ports
$ cat /proc/version
Linux version 4.4.0-999-generic (kernel@tangerine) (gcc version 5.2.1 20151010
(Ubuntu 5.2.1-22ubuntu2) ) #201601122100 SMP Wed Jan 13 02:02:49 UTC 2016
New kernel logs attached
** Attachment added: "success-3s"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/152782
** Attachment added: "fail-20s"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527829/+attachment/4549620/+files/fail-20s
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1527829
Upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=91508
** Bug watch added: freedesktop.org Bugzilla #91508
https://bugs.freedesktop.org/show_bug.cgi?id=91508
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
nSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: derek 2642 F pulseaudio
/dev/snd/controlC0: derek 2642 F
derek@exa:~$ sudo dmidecode -s bios-version && sudo dmidecode -s
bios-release-date
A04
03/19/2014
I'm now posting this from an Android AP just fine. I'd say it were an
issue with just this D-Link router, however the windows PCs using it are
fine. Is there any other way I c
Release: Ubuntu 14.04
Package: linux-image-3.13.0-27-generic 3.13.0-27.50
ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/co
audio
derek 1940 F pulseaudio
Date: Sun Mar 30 16:47:05 2014
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=5b319b83-3d6e-4499-acb3-79f43f98c70e
InstallationDate: Installed on 2014-03-30 (0 days ago)
Installation
Public bug reported:
to make a persistent /root, I'd usually like to rm -rf /root and make it a
symlink to somewhere on the harddrive, when I run with the Ubuntu Studio 15.10
(Wily Werewolf) Daily Build, it just crashed the kernel, this crash didn't
happen of my last visit ubuntu14.10
http://
this looks like a bug of overlay fs, when /root only exists in underlying rofs
and not exist in upper writable layer, what will happen if remove the dir from
the combined mount?
please let me know what else I can do to narrow down this kernel bug.
** Attachment removed: "WifiSyslog.txt"
http
Tested upstream v4.1.1 doesn't have this problem; kernel-fixed-upstream
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1.1-unstable/
[ ] linux-image-4.1.1-040101-lowlatency_4.1.1-040101.201506291635_amd64.deb
29-Jun-2015 20:58 53M
root@ubuntu-studio:~# uname -a
Linux ubuntu-studio 4.
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 2602 F pulseaudio
/dev/snd/controlC1: derek 2602 F pulseaudio
CurrentDesktop: Unity
Date: Sun Mar 15 23:39:06 2015
HibernationDevice: RESUME=UUID=44d65992-42b9-4e97-b78b-0df642d296b2
InstallationDate
u 3.13.0-27.50-generic 3.13.11
Uname: Linux 3.13.0-27-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 2602 F pulseaudio
/dev/snd/controlC1: derek 2602 F pulseaudio
Current
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1469579
I have the Ubuntu Mate Daily Live 20150716 image is good, doesn't have this
problem anymore.
http://cdimages.ubuntu.com/ubuntu-mate/daily-live/20150716/
root@ubuntu-mate:~# uname -a
Linux ubuntu-mate 4.0.0-4-generic #6-Ubuntu SMP Tue Jun 30 20:49:28 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
--
Y
I am running 15.10/beta-2/ on laptop and close laptop everyday (power
suspend / resume only, not shutdown / reboot), and see the problem here
again, once in a while (a few days), the laptop becomes hot, fan start
spinning, then I started top, see kidle_inejct spinning up cpu, this
state can last fo
Public bug reported:
Cheese doesn't work. Google Hangout does not work.
I haven't found much on this issue in Ubuntu 15.10, understandably so.
I have tried the option below. Followed by that is a description of my
system. Then I list the return of lsusb. I do not see my camera
listed. Follow
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev
_dialog_setup_resolutions_for_device: assertion
- 'device != NULL' failed
+ ** (cheese:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
+ ---
+ ApportVersion: 2.19.1-0ubuntu4
+ Architecture: amd64
+ AudioDevicesInUs
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC1: derek
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/con
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC
:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/con
'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 7518 F pulseaudio
/dev/snd/controlC1: derek 7518 F pulseaudio
CurrentDesktop: Unity
DistroRelease:
; expects type 's', but a GVariant of
type '(null)' was given
** (cheese:15224): CRITICAL **:
cheese_preferences_dialog_setup_resolutions_for_device: assertion 'device !=
NULL' failed
---
ApportVersion: 2.19.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia:
@Ken Stone
I had the same issue, using the 142 kernel, successful install but when the
system restarts post install, no network modules
I have just successfully tested using the HWE kernel
d-i base-installer/kernel/image string linux-image-generic-hwe-16.04
--
You received this bug notificatio
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821936
Title:
ALC274 unsupported
Status in alsa-driver packag
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1821936
Title:
ALC274 unsupported
Status in alsa-driver package in Ub
Apologies my first run of apport was mainline 5.0. I immediately
rebooted and use a standard default kernel for 18.04. I deleted both
mainlines since they didn't solve my issue anyway.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
No, my point is that I tried other kernel versions to see if it was
patched. No kernel world with ACL274 on this machine. Windows works
great.
4.18, installed with Ubuntu 18.04.2, to 5.0 were tested with the same
results. The issue persists.
Sorry for the confusion.
How do I get this to stop bei
See post #5 at https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/1784485
It references another Linux variant (eww). But, reading their thread
you will find that they made a patch in December 2018 to solve the 294
issue. Then, the bug report for Ubuntu let to y'all doing the same.
I've
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
r Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: gdm190
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
Insta
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
cesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver&
_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F...
_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek
snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
ERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-03-23 (5 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: gdm1903 F pulseaudio
derek 2464 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: I
nd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Config Status: cfg=new, avail=yes, need=no, active=unknown
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/c
I ran into this exact same problem under Artful after updating to Linux
kernel 4.13.0-38-generic. Can anyone confirm that the fix will be
backported to Artful in an upcoming kernel update?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
Looks like it's in master-next (-31.33). See https://git.launchpad.net
/~ubuntu-kernel/ubuntu/+source/linux/+git/bionic/commit/?h=master-next
and https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/bionic/tree/block/blk-
core.c?id=Ubuntu-4.15.0-31.33#n856
--
You received this bug
op spot for leading OS. You should pay for everyone's notebook
etc. that has to be replaced. Hope you have a truly shit new year just
like you've made others have.
** Changed in: linux (Ubuntu Artful)
Assignee: (unassigned) => Derek Ashby (delsubuntu)
--
You received this bug
Public bug reported:
This machine (I believe) has PAE capabilities (Pentium-M), but 15.10 has become
very unforgiving of machines that don't report PAE flags in /proc/cpuinfo.
I had a royal pain in the behind upgrading from 15.04 (where --forcepae just
did the business) to 15.10 because this p
Working around the problem for now with this:
cat /proc/cpuinfo | sed 's/flags\t*:/& pae/' > /tmp/cpuinfo_pae
sudo mount -o bind /tmp/cpuinfo_pae /proc/cpuinfo
sudo mount -o remount,ro,bind /proc/cpuinfo
But would like a more permanent solution
--
You received this bug notific
Public bug reported:
Probably the PAE issue I reported before again
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: linux-image-4.2.0-23-generic (not installed)
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
Uname: Linux 4.2.0-22-generic i686
ApportVersion: 2.19.1-0ubuntu5
Archi
Same issue here
http://www.reddit.com/r/Ubuntu/comments/23zudj/why_is_ubuntu_networking_so_slow385mbps/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1275161
Title:
Realtek driver r81
I am also having an issue where my system completely locks up. Mouse /
keyboard are unresponsive and I am unable to ssh in from another system.
This is a new build with all new hardware:
ASUS H81I-PLUS Socket 1150 w/ Intel H81 Chipset
Intel Pentium G3220 Dual-Core Processor @ 3.0 GHz
Team Vulcan
#24 > Using inotifywait on /proc works fine too.
False, it does not notify you of new entries (like new processes
launched). Try the program below for proof; launch it and run "sleep
999" and you will not see the PID of your new sleep appear printed out.
Using inotify with /proc/ will probably n
Still there in ubuntu 14.04. We have an idle system with (basically)
nothing going on, and it hovers at 1.0:
ubuntu@build-globallogic:~$ uptime
11:09:18 up 6 days, 18:21, 1 user, load average: 1.00, 1.01, 1.05
ubuntu@build-globallogic:~$ uname -a
Linux build-globallogic 3.13.0-29-generic #53-
Still there in 14.04.
Please be advised, this bug breaks the SSH ControlMaster feature, which
in turn breaks Android builds.
I am trying to use LXC containers (snapshot clones using overlayfs) to
build Android (12.04 container on a 14.04 host). Android's build
utility "repo" is a python script t
There is a similar issue with bindfs (SSH fails with the same error when
using ControlMaster). Maybe it's related. See:
http://code.google.com/p/bindfs/issues/detail?id=27
** Bug watch added: code.google.com/p/bindfs/issues #27
http://code.google.com/p/bindfs/issues/detail?id=27
--
You re
Public bug reported:
Fell over during Software Updater
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
Uname: Linux 4.4.0-28-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i
I also have this bug running 16.04 (4.4.0-34-generic).
Very annoying to have your network just fall out of the sky randomly
when your home directories are remote.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
I to have this bug, I have tried several fixes published about ACPI
kernel settings, none seem to work.
Did anyone try the latest Kernel yet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs
tag: kernel-bug-exists-upstream
kernel-bug-exists-upstream
I have had time to install the upstream Kernel, as per jsalisbury
suggestion. It is exactly the same. The controls move the level up/down
but the actual screen brightness does not change.
I am new to this type of forum and don't know how
h the AMD
13.10-beta2 drivers.
Home this helps.
Derek
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1214752
Title:
Lenovo Ideapad S205] Brightness keys do not change brightness after
Linux Mint 21.1 Cinnamon (vera) NO SOUND OUTPUT
Issue on Intel NUC8i7HVK with AMD Radeon chip works OK with kernel
5.19.0-32 but failed SOUND output after kernel upgraded to 5.19.0.38.39
and also earlier kernel 5.19.0.35.36.
alsamixer shows no sign of the HDA ATI HDMI sound card after the kernel
Yesterday I did an Intel update under w10 (dual Boot) for the realtek
driver and it failed under Intel's install program. I tried a download
version and it repeatedly failed to install properly although it went
through the motions. Upon trying VLC it crashed immediately. It looks
like it might be a
-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC0: derek 1460 F pulsea
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F p
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-04 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla&qu
vicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-04 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy
USERPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-04 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla&qu
RPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-04 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla&qu
RPID ACCESS COMMAND
/dev/snd/controlC0: derek 1460 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 6 20:48:52 2021
InstallationDate: Installed on 2021-02-04 (2 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla&qu
1 - 100 of 114 matches
Mail list logo
