Public bug reported:
A popup window states "Could not calculate the upgrade. An unresolvable
problem occured while calculating the upgrade. If none of this applies,
then please report this bug using ...
* It does not matter whether I am using the UI dist-upgrade or command line
tool.
* First
I don't use it much but since corradoventu went to the trouble it
affects me as well.
"PRETTY_NAME="Ubuntu Oracular Oriole (development branch)"
NAME="Ubuntu"
VERSION_ID="24.10"
VERSION="24.10 (Oracular Oriole)"
VERSION_CODENAME=oracular
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/;
This will disable it for the current session:
**" rfkill list
0: ideapad_wlan: Wireless LAN
Soft blocked: yes
Hard blocked: no
1: ideapad_bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3:
I forgot this that "might" help.
**" systemctl stop bluetooth.service
┌───>
│~
└─>
(wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **: 09:49:15.181: Unable to
replace properties on 0: Error getting properties for ID
(wrapper-2.0:231189): LIBDBUSMENU-GLIB-WARNING **:
Public bug reported:
systemd stop bluetooth.service no longer stops bluetooth.
And systemd disable bluetooth.service, restarts after reboot
"systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset>
Public bug reported:
After Fresh install of UbuntuStudio v22.04 from thumb drive, receive
this Error filling up the screen.
Managed to write down the Error, screen fills up with ...
"UBSAN: array index out of bounds in /var/lib/dkms/virtualbox
6.1.50/build/vboxdrv/SUPDrvGip"
and Fails to Boot.
Update: this is strangely related to nouveau
On a machine with a "NVIDIA MCP89 [GeForce 320M]" the nvidia drivers have been
removed from 22.04. nouveau when run normally now causes a hang [see other
reports if curious]
The described "firewire_ohci quits when using firefox" happens when kernel
** Attachment added: "screen-2024-04-24-17-49-34.png"
https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/2063357/+attachment/5770120/+files/screen-2024-04-24-17-49-34.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Thank you for the timely reply.
I assumed the support site was a report, my apologies, as I assumed it was
monitored.
I found a very similar report, which I presume is "proper", here:
https://bugs.launchpad.net/ubuntu/+source/lxqt-powermanagement/+bug/1987036
and indeed this is a few days older
Public bug reported:
I have exactly the same problem as OP here (and the others who chime in):
https://askubuntu.com/questions/1422776/energy-manager-error-when-reducing-screen-brightness-during-inactivity
Reported 1 year 8 months ago, still seems broken
LxQT Power Manager:
In the settings
Public bug reported:
This began in 6.5.0-27 afaict, and is very noticeable in 6.5.0-28
Using snd_dice to playback audio, doing anything else, even just scrolling in
firefox or launching this bug report, causes the firewire driver to quit:
Apr 23 12:48:53 Konnekt kernel: firewire_ohci
I have found a fix.
First I tried adding "nouveau.modeset=0" to bootflags, which got me to boot but
no greeter.
sddm appeared to be happily running but it failed to start the display server
restarting it did not help
"startx" worked, which gave me hope
It appeared the session "seat" had been
This is the closest, most recent report I could find with something which also
appears kernel related
Kernel 6.5.0-27 -- works fine
Kernel 6.5.0-28 -- graphics hard-hangs - sddm never displays, vtty can't be
activated
shh works, sddm and x11 processes can not be killed, reboot hangs, hard
*** This bug is a security vulnerability ***
Public security bug reported:
This is first boot after install on a KVM current iso dated today.
ProblemType: Crash
DistroRelease: Ubuntu 24.04
Package: xfce4-settings 4.18.4-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname:
I tried Ubuntu 22.04 with kernel 5.13 on Acer Spin 5 SP513-54N.
Touchpad, touchscreen, and stylus all work, but Wi-Fi does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970056
Title:
Public bug reported:
The gutenprint website says that they still support the earlier "Epson
Stylus Photo" models, but the Ubuntu printer settings tool only shows
drivers for the R240 and up. Is this a regression, or purposeful? See
http://gimp-print.sourceforge.net/p_Supported_Printers.php
The
Is this Linux patch series back-ported to older kernels, like the 5.13
kernel that came with my Ubuntu 20.04 installation, or any LTS kernel?
I'm not fully familiar with the Linux kernel release behaviour.
I'm asking this because I'm looking for the best way to apply this patch
on an older kernel
I just verified the patch in Ubuntu 20.04 under kernel version 5.13. All
of my components now show up in open RGB. I compiled the kernel myself
using the steps provided in
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651.
As mentioned above, I was not able to verify the PPA
I am now building the kernel from source using the following steps
https://gitlab.com/CalcProgrammer1/OpenRGB/-/issues/1984#note_872699651
to verify whether the patch solves my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah yea, that's a type. I used `sudo reboot now`. For me, after those
steps the ram still didn't show up, so there might be another problem on
my system. I also tried manually building the kernel with the patch, but
I run into some unrelated issues. I think I will wait till the patch
hits the
I tried the PPA from @vicamo on Ubuntu 20.04 with kernel 5.14, but It
does not seem to work for me. I installed the PPA using the following
commands:
sudo add-apt-repository ppa:vicamo/ppa-1950062
sudo update`
sudo install linux-oem-5.14-headers-5.14.0-2023
linux-oem-5.14-tools-5.14.0-2023
I am affected by this issue on my Ubuntu 20.04 system that is running
kernel a 5.13 kernel. I have a ASUS rog stix b550-E gaming motherboard,
an AMD 5600G CPU and use crucial ballistix ram.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Daniel .. Thanks.
* I think brightness-controller is a thin UI around xrandr. If something in
Ubuntu is improperly changing "Brightness" and xrandr is the only cure, why
remove brightness-controller? Or, do your comments about it apply equally to
xrandr -- namely that I should avoid xrandr,
Public bug reported:
I walk away from the machine; come back hours later to find that the
screen is dim. The following command confirms that the cause is
something in Ubuntu
xrandr --listmonitors --verbose | egrep -3 -i 'gamma|backl|brightn'
Has shown value for "Brightness" of 0.11, 0.18,
I'm not sure what's needed to bisect the kernel? What would I need to
do?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Public bug reported:
failed to install through command lines
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: am-utils 6.2+rc20110530-3.2ubuntu2
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
The speed is limited on every boot now...I also notice my bios time
being reset to 2013...when unplugged from the wall (I'm going to open it
up, the cmos battery may have died.)
rt@sys76:~$ sudo grep . /sys/class/powercap/intel-rapl/intel-rapl\:0/*
[sudo] password for rt:
@koba issue still occurs.
@Doug
rt@sys76:~$ sudo rdmsr -c -p0 0x1b2
0x3
rt@sys76:~$ sudo strace rdmsr 0x1b2
execve("/usr/sbin/rdmsr", ["rdmsr", "0x1b2"], 0x7fff4f90a298 /* 17 vars */) = 0
brk(NULL) = 0x56510cc31000
arch_prctl(0x3001 /* ARCH_??? */,
ok
rt@sys76:~$ sudo rdmsr -c -p0 0x19c
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x1aa
0x40
rt@sys76:~$ sudo rdmsr -c -p0 0x1b1
0x8839080c
rt@sys76:~$ sudo rdmsr -c -p0 0x16f
rdmsr: CPU 0 cannot read MSR 0x016f
rt@sys76:~$ sudo rdmsr -c -p0 0x1fc
0x4005d
rt@sys76:~$ sudo strace rdmsr
Ok
One terminal was running
rt@sys76:~$ taskset -c 2 yes > /dev/null
2nd terminal data:
rt@sys76:~$ grep . /sys/devices/system/cpu/intel_pstate/*
/sys/devices/system/cpu/intel_pstate/max_perf_pct:100
/sys/devices/system/cpu/intel_pstate/min_perf_pct:50
Now after another reboot the speed is stuck at 800mhz again and doesn't
move
rt@sys76:~$ uname -r
5.15.5-76051505-generic
rt@sys76:~$ grep CONFIG_CPU_FREQ_DEFAULT /boot/config-5.15.5-76051505-generic
# CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE is not set
# CONFIG_CPU_FREQ_DEFAULT_GOV_POWERSAVE is
Yes I can get it to boot into active mode thanks to Doug, but after
several minutes the cpu drops to 798-800mhz and won't increase no matter
if I try and change it. I did notice that the scaling_governor always
boots to powersave mode. When I change it to performance after several
minutes the
Here's a list I can't remember the last time it worked, if you do a
google search on "ubuntu cpu lowest freq" seems to be a very common
problem but none of the fixes work for me.
I can't change the speed of my CPU's in my bios (a system76 linux machine).
What do you want me to check in the
ok...
rt@sys76:~$ sudo cpupower -c all frequency-info
[sudo] password for rt:
analyzing CPU 0:
driver: intel_cpufreq
CPUs which run at the same hardware frequency: 0
CPUs which need to have their frequency coordinated by software: 0
maximum transition latency: 20.0 us
hardware limits:
rt@sys76:~$ sudo systemctl status thermald.service
● thermald.service - Thermal Daemon Service
Loaded: loaded (/lib/systemd/system/thermald.service; enabled; v>
Active: inactive (dead) since Wed 2021-12-01 09:39:26 EST; 9s ago
Process: 1319 ExecStart=/usr/sbin/thermald --systemd
I'm not sure if this is the right package
** Package changed: ubuntu => thermald (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at minimum value..again
Public bug reported:
I would really like to find out why my cpu's keep reverting back to a cpu
powersave mode after I get a kernel update then reboot.
I cleaned my laptops vent but this seems to happen whenever a new kernel
is updated and installed.
Thanks for this fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935767
Title:
vanilla-gnome-default-settings will not install for impish-proposed
To manage notifications about this bug go to:
Stuart Marks (from the Open JDK team) has found the problematic code in
https://packages.debian.org/unstable/java/openjdk-16-source and
identified two bugs in it, including the one responsible for this
behavior. For that bug, he has recommended a fix. Please see his
analysis at
** Summary changed:
- Security exception raised by java.util.Properties.store() when using
openjdk-16-jdk-headless
+ Security exception raised by java.util.Properties.store() when using
openjdk-16-jdk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Since JDK 11, the Ubuntu "open jdk" packages have a defect which does
not appear in the actual Open JDK distros available from java.net. The
problem was discovered by Derby users (see
https://issues.apache.org/jira/browse/DERBY-7122) and reported as an
Open JDK bug (see
VersionSignature: Ubuntu 4.4.0-211.243-generic 4.4.262
Uname: Linux 4.4.0-211-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.30+esm1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: rick 2218 F pulseaudio
/dev/snd/controlC0: rick 2218 F pul
Public bug reported:
PC：Lenovo YOGA 14C Intel EVO CPU：i5-1135G7
sound card：
cat /proc/asound/cards
0 [sofhdadsp ]: sof-hda-dsp - sof-hda-dsp
LENOVO-82DG-Yoga14cITL2021-LNVNB161216
others info：
inxi -SMA
System:Host: rick Kernel: 5.8.0-53-generic x86_64 bits
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
???@???-OMEN:~$ lsb_release -rd
Description: Ubuntu 21.04
Release: 21.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by
Dell Latitude-9520 has the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924685
Title:
No sound output/input available after installing 21.04
To manage notifications about this bug go
I agree
I think the default behavior in Nautilus Preferences should be "Ask what
to do" for "Executable Text Files"
gsettings set org.gnome.nautilus.preferences executable-text-activation
ask
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
[Summary]
Internal speaker doesn't work after plug in a headset. In the meantime, audio
for HDMI/Buletooth headset/wired headset are working fine. Only Internal
speaker doesn't work. But internal speaker working well if not plug wired
headset in.
+ CID:202010-28313
Public bug reported:
[Summary]
Internal speaker doesn't work after plug in a headset. In the meantime, audio
for HDMI/Buletooth headset/wired headset are working fine. Only Internal
speaker doesn't work. But internal speaker working well if not plug wired
headset in.
ProblemType: Bug
Public bug reported:
In the Kubuntu installer I choose guided encrypted LVM install and after
clicking "Install Now" ubi-partman crashes with exit code 141.
Choosing "Guided - use entire disk" does work without a problem.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.12
> What is the impact of this? It seems to happily install PEP 517
packages as-is.
@Stefano sorry for the delay here. Installing PEP517 packages is fine
without the patch, but building them (building a wheel) is where the
issue comes in.
If you need a concrete example, download the .tar.gz of any
The impact of the pep517 issue isn't too big of an issue for us- we can
work around it (installing toml).
The "impact" is that we have a test scenario which runs `pip install
pep517` (reports already installed) and then tries to do `python -m
pep517.build --binary --out-dir dist .` (which fails
Sorry, posted that from the wrong account, that comment was by me (the
original bug reporter).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880749
Title:
python3 virtualenvs include (broken)
Public bug reported:
I absolutely needed look behind functionality, and it would not work in
kate and kwrite. I finally solved the problem by opening the text file
in libreoffice writer -- look behind is working there.
** Affects: kate (Ubuntu)
Importance: Undecided
Status: New
I switched display managers from lightdm to gdm and it fixed the issue
sudo systemctl status display-manager
sudo dpkg-reconfigure lightdm
systemctl status gdm.service
sudo apt install --reinstall ubuntu-session
reboot machine
Info about the issue:
I get false
rt@sys76:~$ gsettings get org.gnome.desktop.lockdown disable-lock-screen
false
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153
Title:
I upgraded from 18.04 to 20.04.1 and the
Public bug reported:
Ubuntu 20.04.1 LTS
mosquitto 1.6.9-1
I have a MQTT-brokered weather station, which sends realtime updates to
a webpage using paho to do MQTT over websockets
Everything worked fine until upgrade from bionic to focal
The mosquitto broker continued to work fine, but the
Sure
The Keyboard Shortcuts for Lock Screen is set to Ctrl+Alt+L
Found in Settings -> Keyboard Shortcuts -> Lock screen -> Ctrl+Alt+L
1) I can't lock the screen using the (keybinding / shortcut) Ctrl+Alt+L
https://i.imgur.com/VKiXvZV.png
2) I can lock the screen by clicking on the lock option
1. The specific steps or actions you took that caused you to encounter
the problem.
-I tried to set the screen to lock at a specific interval and it doesn't lock
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> Enabled
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock -> 30
Should be:
Settings-> Privacy-> Screen Lock -> Automatic Screen Lock Delay -> 30 seconds
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153
Title:
I upgraded from 18.04 to 20.04.1 and the
The options for locking, blanking and shortcut keys are in the gnome-
control-center
** Package changed: ubuntu => gnome-control-center (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153
rt@sys76:~$ uname -a
Linux sys76 5.4.0-48-generic #52-Ubuntu SMP Thu Sep 10 10:58:49 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1898153
Title:
I upgraded
Public bug reported:
I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go
blank at the set time. I think this issue also effects the shortcuts
not working also.
I'm using nemo as my file manager I followed these instructions below
Hey Jackson
Thanks for feeding back on this. I'll do an install and retry the repo
steps, hopefully its fixed.
Rick
On Fri, 25 Sep 2020 21:59 Jackson Doak, <1579...@bugs.launchpad.net>
wrote:
> I cannot reproduce this in 20.10, can someone reproduce in any remaining
> suppor
oved and new flash drive inserted. That one was also immediately
> recognized and mounted and then suddenly it disappeared from view. Now
> the drive itself is not found and nothing is mounted or installed when
> inserted into that port (neither flash drive nor an external mouse).
>
>
when
inserted into that port (neither flash drive nor an external mouse).
Ubuntu Release 20.04.1 LTS' 64-bit GNOME 3.36.3
Rick Feldman
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname
** Changed in: gamemode (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880784
Title:
Gamemode sets incorrect default governor
To manage notifications
Public bug reported:
gamemode 1.5.1-0ubuntu3 in Ubuntu 20.04 LTS
Gamemode sets the incorrect default cpu governor which causes huge
performance decreases in some scenarios.
What I expect to happen:
Gamemode on exit should set the cpu governor back to system default (ondemand
in Ubuntu's case I
Public bug reported:
On a clean 20.04 machine (or container), observe the following:
apt-get update
apt-get install -y python3-virtualenv
python3 -m virtualenv foo && source foo/bin/activate
pip list
You will notice there are a plethora of extra packages in the virtual
environment that should
to enhance the man page
with a mention of how to properly log in /etc/msmtp.
Thanks again.
On 5/6/20 4:23 PM, Simon Déziel wrote:
> On 2020-05-06 4:09 p.m., Rick Poleshuck wrote:
>> I will try that. If that works,
> It's what I use on all my machines.
>
>> then the bug is only
I will try that. If that works, then the bug is only in the
documentation referencing /var/log/msmtp.
On 5/6/20 3:40 PM, Simon Déziel wrote:
> The msmtp group was created to allow one to protect /etc/msmtprc from
> regular users as it can contain plaintext passwords. If you join users
> to that
Public bug reported:
installation error
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
As an enhancement, I also created a logrotate profile for the log file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876496
Title:
Using /var/log/msmtp for all users is broken
To manage
. Logging to users home
directory works fine.
Ubuntu release: Ubuntu 20.04 LTS
Package: msmtp/focal,now 1.8.6-1 amd64
Thanks to the development team for this great product.
Rick Poleshuck
** Affects: msmtp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
20.04 beta still has this issue for me
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia] Automatic login fails and then all subsequent logins fail.
Killing
Public bug reported:
All workspaces in Gnome are showing phantom windows from all other
workspaces.
Steps to reproduce:
1
- Have any program(s) open on any workspace(s)
- Switch to another workspace via the Activities Overview
- Phantom window(s) from all other workspaces are there
2
- Switch
Public bug reported:
grup would not go onto windows boot manager so I deleted windows boot
manager so Ubuntu Boot might be Primary boot package on win 10 on Dell
3750.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu
Broken in 20.04 also, but now it shows this error message "Sorry! There
are no details for that application"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857814
Title:
"Show details" option
A 32bit build would be greatly useful for use with Lutris.
Lutris has a gamemode toggle in their program, but it requires both 32bit and
64bit gamemode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
For Snap programs if you right click and "Show Details" in Gnome it will
open Ubuntu Software and come up with an error message "Sorry! There are
no details for that application"
Expected outcome when clicking "Show Details" should be Ubuntu Software
being opened to the
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
Same problem on 18.04 with Sony headset:
s
[WI-1000X]# info 38:18:4C:04:C7:2A
Device 38:18:4C:04:C7:2A (public)
Name: WI-1000X
Alias: WI-1000X
Class: 0x00240404
Icon:
@albertomilone: That does not work. I still cannot auto-login after
adding
needs_root_rights = yes
in /etc/X11/Xwrapper.config
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845801
Title:
[nvidia]
Public bug reported:
At normal boot
If use xorg driver display remain black after boot
If use nvidia driver display and keyboard backlight flickers
At recovery mode
Boots normally
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu
I did some more testing and just removing splash fixes the issue for me.
I edited
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
sudo update-grub
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm having this login loop issue.
Fresh install of 19.10 booted the first time fine, after the first
update and reboot I started getting the login loop.
I'm using an Nvidia GT-1030 and installed the proprietary drivers during
the install.
I removed quiet splash and added nomodeset to grub and
Public bug reported:
Ubuntu 19.10 beta - fresh install Oct 1st image
gnome-software 3.30.6-2ubuntu10
The "Updates" tab on Gnome-Software shows that "Software is up to date"
after clicking the refresh button.
This is not true as there are updates needed, viewable with apt and the
separate
I had this issue in VM consistently when loggin in with Xorg. No problems with
Wayland.
Tried the patch from above ppa and it appears to have solved problem.
Will do physical install on laptop to verify
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
unity-lens-applications "Ubuntu 16.04.6 LTS"
I have two monitors stacked above/below. Launcher set for bottom and
available to be seen on both monitors. If the SUPER key is hit while the
mouse is in the upper monitor window the mouse is able to click on any
icon loaded via
Public bug reported:
nvidia-340 340.107-0ubuntu0.16.04.2: nvidia kernel module failed to
build
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic x86_64
Public bug reported:
fails to build after kernel update.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
Public bug reported:
nvidia kernel module fails to build each kernel update.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-150.176-generic 4.4.179
Uname: Linux 4.4.0-150-generic x86_64
NonfreeKernelModules:
Public bug reported:
NVidia fails everytime a new kernel update is released.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-150.176-generic 4.4.179
Uname: Linux 4.4.0-150-generic x86_64
NonfreeKernelModules:
Public bug reported:
This bug is related to Bug #1773687
I am trying to automate the build of an AMI with a package that requires
tzdata. I am blocked from automation because tzdata will not install
non-interactively. This is despite setting
DEBIAN_FRONTEND=noninteractive.
Here is an
Public bug reported:
Attempting upgrade from 16.04 LTS
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 237-3ubuntu10.11
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
systemd:
In addition to above commit
255095fa7f62ff09b6f61393414535c59c6b4cb0
media: dvb-usb-v2: Fix incorrect use of transfer_flags URB_FREE_BUFFER
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800238
Sorry I meant 4.20.1
** Tags removed: kernel-bug-exists-upstream
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800238
Title:
TechnoTrend TT-TVStick CT2-4400
Kernel 4.21.1 and 4.19.14 have all the fixes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800238
Title:
TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
To manage
** Package changed: ubuntu => gkrellm (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1785406
Title:
Random applications window freezes or stutters
To manage notifications about this bug go
4.18 EOL now anyway
The only way out is to revert the above commit this patch isn't yet upstream
https://patchwork.linuxtv.org/patch/53155/
Also this patch which has made into kernel 4.18
commit 7d95fb746c4eece67308f1642a666ea1ebdbd2cc
Revert "media: dvbsky: use just one mutex for serializing
-a-toplevel-object-on-
glade-crashes-it/46507 ). However, I am NOT using wayland:
$ env | grep XDG_SESSION_TYPE
XDG_SESSION_TYPE=x11
Thanks for looking into this. Rick
** Affects: glade (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800238
Title:
TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel
1 - 100 of 3564 matches
Mail list logo
