*** This bug is a duplicate of bug 1717878 ***
https://bugs.launchpad.net/bugs/1717878
sudo apt install --reinstall ubuntu-session
worked for me as well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Got it, thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically unlock login keyring after recent
updates in noble
To manage notifications about
Same issue here. I don't understand the status, "Won't fix"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060575
Title:
gnome-keyring fails to automatically unlock login keyring after recent
Public bug reported:
The ssd I was attempting to install had a fresh win 10 installed and
updated. This is a brand new system, I used memory and ssd's from the
old system.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.20
ProcVersionSignature: Ubuntu
Should I still submit logs?
I think I'll just buy a new PC w/o NVIDIA and re-purpose this one...
Here is the latest
Lockup 070244 - SSL not avail
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5758328/+files/prevboot.txt
--
I see the status change of the bug. Did the logs finally show anything?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
17:15:47 - SSL not avail
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5757691/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Got it. Testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
9:14:36 No SSL Possible. Attached.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5756414/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Trying to upload the latest file. It's 1.3 G
Uh oh!
Something has gone wrong. We're sorry!
If we are in the middle of an update, Launchpad will be back in a couple
of minutes. Otherwise, we are working to fix the unexpected problems.
Check @launchpadstatus on Twitter or
I'm not sure how to do this:
"drm.debug=0xff loglevel=8"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
Came in this morning and it was locked up. NO SSH.
Going to move back to 6.5
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755959/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
What kernel do you suggest.
Disabling NVIDA isn't an option. I need all 4 monitors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this
130538 full lockup, no ssh available.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755711/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
110230 - Locked up, but instead of staying locked up the desktop crashed
and took me to the login screen.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755691/+files/prevboot.txt
--
You received this bug notification because
uname -r
5.19.17-051917-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
Still lockups- No ssh
18:08:04 attached
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5755386/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ok, running 6.8.
uname -r
6.8.0-060800rc7-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
Newest or a specific one?
Never locks up if I run Windows and passes all hardware testing
(repeated testing for overnight/ several passes)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Should I continue to report this? Is there anything else?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
Ssh works fine until it freezes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
And another. Crash at 85128
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754304/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is the latest crash file.
Unresponsive - even trying ssh won't work
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2054121/+attachment/5754028/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I am running the x.org X server Nouveau display driver now. I will
advise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go
Use x.org X server Nouveau dissplay drivers?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
Latest lockup - 14:22:51
Non responsive k/b & mouse
Can't SSH in after the computer locked up.
It's 100% locked up.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5753901/+files/prevboot.txt
--
You received this bug notification because you
Will do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2054121/+subscriptions
11:51:05 is latest crash.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5753421/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
8:06:14 was time of crash.
I ran the commands.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug go to:
I spoke too soon. Here is the latest file. I will continue with your
instructions now.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5753367/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs,
The mouse freezes as well.
Currently, I am using 545 proprietary. So far I have 18:48 of uptime. I
am going to continue to run to see if it crashes before deleting
extensions. I'll report back.
Of course in the meantime there have also been some small updates as
well.
--
You received this bug
4:49:41 with NVIDIA 545 Driver (open kernel)
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752838/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
BIOS Update didn't resolve anything.
New lockup at 21:13:20
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752677/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Looks like there is a new BIOS available for this PC. I updated to
M3JKT3DA/1.0.0.61.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about
19:31:51
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752648/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
19:27
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752647/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
18:44:29
Sadly, issue persists.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752623/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In UBUNTU IRC Chat two things were suggested:
Uninstall Brave Browser
Disable hardware acceleration on Firefox browser. (The browser I am using).
I was using Chrome and had tried disabling hardware acceleration on it
to troubleshoot. That didn't help which is why I switched to Firefox.
It never
18:13:11
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752622/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
1724 / 1725
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752611/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
11:51:23
Attached file
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752524/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Is any of this helpful? Is there anything else I can do? (Other than
buying a new computer without an NVIDIA card!?!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To
17:45 or 17:46. I didn't get the exact time.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5752214/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ubuntu on Wayland still crashes. I have tried various different versions
of the NVIDIA drivers before and it makes no difference. Here is another
prevboot.txt file.
Lockup at 17:50:44
** Attachment added: "prevboot.txt"
Unplugging the 4 TB HD didn't stop the freezes.
Now running Ubuntu on Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Random Freezing
To manage notifications about this bug
Ok, I have unplugged the WD 4TB drive.
I am going to be having surgery tomorrow so you may not hear back from
me for a couple of days. As soon as I can report back I will. Thanks for
your help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
And another...
16:27:38
I waited over 30 seconds.
I pressed ALT + PrtSc + S several times.
Here is the log.
Still nothing in /var/crash
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749883/+files/prevboot.txt
--
You received this bug
16:11:59
I waited over 30 seconds.
I pressed ALT + PrtSc + S several times.
Here is the log
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749882/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
I can try that, however, every time it has locked up in the past, it is
100% unresponsive. I have run extensive hardware diagnostics and nothing
is wrong. I ran Windows just to test things and no lockups. So it's for
sure something not 100% compatible with Linux.
--
You received this bug
1 - 14:38:34
2 - Done
3 - Done
4 - Attached - See above
5 - /var/crash is empty
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749577/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Prevboot
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+bug/2054121/+attachment/5749206/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054121
Title:
Public bug reported:
Random freezes
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error:
Public bug reported:
Nothing more. Just freezes all the time.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8
Uname: Linux 6.5.0-21-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
Public bug reported:
xmessage text gets obscured with option combinations using buttons and
geometry specifications.
Quick background: xmessage creates a new grey window with a white text
box inside it. Without -buttons, the white text box usually spans the
full width of the grey window that
This bug is fixed in the GIT repository at
https://github.com/gregkh/usbutils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971750
Title:
lsusb shows wrong/duplicate product name
To manage
Public bug reported:
lsusb incorrectly labels a device using the product name from a previous
device.
In the listing below, the incorrect product name on the second 04d8:fee9
device ("Microsoft® LifeCam HD-5000") is a copy of the product name
of the first device in the list:
$ lsusub -s 3:
I'm having the same issue with an RTX 2080. If I start up in safe
graphics mode, it works. But of course then I get degraded graphics.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969959
Title:
Public bug reported:
Apr 12 14:55:05 desktoppc systemd[10265]:
snap.slack.slack.d05ba551-36a5-48a1-b9c7-e694c5e1256d.scope: Failed to add PIDs
to scope's control group: Permission denied
Apr 12 14:55:05 desktoppc systemd[10265]:
snap.slack.slack.d05ba551-36a5-48a1-b9c7-e694c5e1256d.scope:
Public bug reported:
This is a bug in both version `1.0.4` and version `1.0.5_master`.
See https://github.com/firehol/iprange/issues/31
First, set up two test files:
~
$ cat
I am not arguing about the behaviour, which is correct and apparently hasn't
changed.
I'm complaining about the unannounced change in message from "is uptodate" to
"is newer".
Three problems:
1. The message "is newer" is an unannounced change from all previous
versions of rsync that say "is
Public bug reported:
rsync 3.2.3 has a broken "--update" option.See the examples below.
The "--update" option incorrectly makes rsync say a file is newer than itself.
Remove the "--update" option, and rsync correctly says the file is "uptodate".
The right output should of course be "is
Description:Ubuntu 20.04.4 LTS
Linux linux 5.13.0-35-generic #40~20.04.1-Ubuntu SMP Mon Mar 7 09:18:32 UTC
2022 x86_64 x86_64 x86_64 GNU/Linux
Mar 11 10:43:28 linux kernel: [1.578010] usb usb6: We don't know the
algorithms for LPM for this host, disabling LPM.
Mar 11 10:43:28 linux
Public bug reported:
The rsyslog program mis-handles the "startswith_i" comparison when applied
to $programname. Details follow:
Put this file in /etc/rsyslog.d/10-idallen.conf (it precedes all other
files):
if ( $programname startswith 'foo' ) then {
/var/log/idallen-cron.log
Public bug reported:
The script /usr/lib/update-notifier/update-motd-fsck-at-reboot contains some
coding errors.
One of the errors hides the other error:
1. It sets two variables NEEDS_FSCK_CHECK and NEED_FSCK_CHECK (missing
'S') but only checks one of them (NEEDS_FSCK_CHECK). Because of this
Now that I think of it, that's qualitatively no different than running
"vim.tiny"...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873920
Title:
default vi on focal emits escape sequences
Workaround:
ex file
visual
("visual" can be abbreviated as "vi")
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873920
Title:
default vi on focal emits escape sequences unrecognized by bionic's
Confirmed on Ubuntu Focal (Kubuntu 20.04) installed on LVM disk, with
GRUB_SAVEDEFAULT=true
This bug triggers whenever a boot option other than the first is being
selected in the grub menu. grub won't be able to save that selection.
--
You received this bug notification because you are a member
If you could at least document what "/fsstnd" is (when the mandb man
page says FSSTND should use /var/catman not /fsstnd), and why /usr/man
and /usr/share/man are different and must look in different places in
the MANDB_MAP, then maybe the current behaviour wouldn't look like a bug
but a feature.
Public bug reported:
In the old days, man pages were stored under /usr/man. Now, they are
stored under /usr/share/man. Ubuntu systems no longer have a /usr/man,
so all our really old scripts and reflexes that look under /usr/man fail
unless you think to add the helpful symlink "ln -s share/man
Public bug reported:
The /etc/cron.monthly/acct cron script is run monthly by cron or anacron
to "perform monthly login accounting" with the /var/log/wtmp file.
The cron script only works correctly if the wtmp file is rolled exactly
monthly and gives errors otherwise. Fixing the script to do
I'm now getting radeon GPU lockup with the Ubuntu 5.11.0-25 and 5.11.0-27
kernels.
The 5.8.0-63 kernel and all previous work fine.
$ lspci | grep ATI
05:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620
GL [FirePro 2450]
06:00.0 Display controller: Advanced Micro
Public bug reported:
The Debian people tell me this bug was fixed Upstream six months ago.
Ubuntu 20.04 LTS systems have the atop/acct conflict problem where if
you install acct it wants the pacct file in one place
(/var/log/account/pacct) and then if you install atop it starts
atopacctd that
In Ubuntu 20.04 LTS the script /etc/init.d/atop calls
/usr/share/atop/atop.daily which does read /etc/default/atop and uses
the variable LOGGENERATIONS=28. Systemd
/usr/local/lib/systemd/system/atop.service also calls
/usr/share/atop/atop.daily.
Confusingly, the file /etc/default/atop says not
Public bug reported:
"ts -r" does not recognize three of the eleven example formats given in
the man page for Perl Date::Parse. In particular, it doesn't recognize
the standard ISO-8601 format "1995:01:24T09:08:17.1823213":
$ ts -r
1995:01:24T09:08:17.1823213
1995:01:24T09:08:17.1823213
Public bug reported:
I'm trying to test systemd-cryptenroll with FIDO2 keys in the new
systemd version 248 on impish.
Running "systemd-cryptenroll --fido2-device=list" results in the
message:
FIDO2 tokens not supported on this build.
Would it be possible to build systemd with FIDO support in
** Changed in: launchpad
Assignee: Carlos Perelló Marín (carlos) => (unassigned)
** Changed in: launchpad
Assignee: (unassigned) => David Allen Arteaga (dirty-alpha-85)
** Also affects: ubuntu
Importance: Undecided
Status: New
** Also affects: ubuntu-leb
Impo
Public bug reported:
release:
Description:Ubuntu 20.04.2 LTS
Release:20.04
gdb:
Installed:
I wonder if the recent Gnome 3.38.5 update addresses this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922353
Title:
Overview sometimes fails to appear or disappear in 21.04
To manage
There seems to have been some issue during the upgrade that blocked the
creation of the PID file. Manually killing the exim process and re-
starting it seems to have fixed the issue.
Apologies for the noise!
** Changed in: exim4 (Ubuntu)
Status: New => Invalid
--
You received this bug
Public bug reported:
Since the latest release, no PID file is created in /run/exim4/exim.pid
when Exim is run.
No local configuration changes have been made between the working and
non-working versions. The command line arguments are '/usr/sbin/exim4
-bd -q30m', and there are no PID-related
Public bug reported:
sudo apt upgrade went not according to plan
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: nvidia-kernel-common-460 460.32.03-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18
Uname: Linux 5.8.0-34-generic x86_64
NonfreeKernelModules:
Damn doesn't seem to be a close or delete option. Daniel could you
please do the honours?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1909946
Title:
Gnome Wayland session starts, then quits.
To
Daniel I was pretty sure that the problem existed in my home directory. So,
rather than go through all the gnome gnome settings one by one, with subsequent
reboots, I cleaned out my home directory of all gnome specific settings at once
this am, and rebooted and problem is gone - I'm now in
Regarding Item #3: Didn't know /var/crash existed, thanks for the heads
up with the article too.
I browsed /var/crash, there are quite a few files (18) from yesterday
and today. Now none dated Jan 04 matched XWayland, however 2 from
yesterday. The more recent ones (Jan 04) mention 'Blueman
Thanks Daniel, yes I meant a crash, just different wording.
OK Attached is the file with all extensions disabled. If I'm reading the
file correctly it seems to be a snap issue with an app not autostarting?
Anyway lots of errors but when I scrolled down to the bottom showing the
most recent boot
Some more details: Using both gnome-wayland & ubuntu-wayland sessions,
the common major errors are the following:
12:22:45 PM gnome-shell: Can't create a GtkStyleContext without a display
connection
12:22:23 PM gdm-session-wor: gkr-pam: unable to locate daemon control file
It happens when the
Public bug reported:
So, this started about a week ago after an update from Ubuntu. I can
initially login with XWayland, but something loading after the desktop
appears, causes the session to exit. The only thing I can find relevant
in the logs at the timestamp this occurred are the following:
Public bug reported:
Since this is from the Universe repo, should I report this upstream
instead of here? Please advise. App was fine 24 hours ago, so recent
updates might have a bearing on this.
Running from a shell:
:~$ tootle
[INFO 08:17:28.652378] Application.vala:156: Tootle version: 0.2.0
Public bug reported:
Shouldn't these give the same results in dash, i.e. "/root"?
They give the same output in bash.
$ dash
$ var=~root
$ echo "$var"
/root
$ export var=~root
$ echo "$var"
~root
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: dash 0.5.10.2-6
ProcVersionSignature: Ubuntu
Public bug reported:
When run from terminal:
tootle
[INFO 14:53:00.814180] Application.vala:156: Tootle version: 0.2.0
[INFO 14:53:00.814200] Application.vala:158: Kernel version: 5.9.1-xanmod1
[INFO 14:53:00.826796] Notificator.vala:40: Starting:
/api/v1/streaming/?stream=user
[INFO
This problem persists with Ubuntu 20.10 released today.
The modprobe/rmmod/modprobe method above still works there, however it
is very inconvenient to have to perform those steps after each reboot.
Unfortunate, as Ubuntu has been the distro that I've used and
recommended to others for the last
Seems we need that downstream too, then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884295
Title:
AttributeError: 'QWebEngineProfile' object has no attribute
'setUrlRequestInterceptor'
To
876...@bugs.launchpad.net>
wrote:
> @Stephen Allen (stephen-d-allen),
>
> Are you using snaps or debs? I'm wondering if the snap structure is
> different and would account for you not having it in that location.
>
> Can you try something like:
>
> sudo dpkg -L clamtk
>
> Thanks,
>
Yeah ... not there either. I'll get back to it later on this evening.
On Sun, Aug 16, 2020 at 10:30 AM Dave M <1876...@bugs.launchpad.net>
wrote:
> Ok, on Ubuntu 18.04 it's this:
>
> /usr/share/perl5/ClamTk/
>
> I don't have 20.04 installed yet.
>
> --
> You received this bug notification
On Ubuntu LTS 20.04 I don't have that path - see screengrab. Thanks.
** Attachment added: "screengrab of my Perl5 directory"
https://bugs.launchpad.net/clamtk/+bug/1876497/+attachment/5401948/+files/Aug16-2020.png
--
You received this bug notification because you are a member of Ubuntu
I have also encountered this issue:
Parsing all content...
CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [9:11: $]
CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [16:12: $]
CSSStyleDeclaration: Unexpected token, ignoring upto '$698: False;'. [18:12: $]
Public bug reported:
I was installing Ubuntu from usb stick and it crashed
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: wl zfs zunicode zavl icp zcommon
Public bug reported:
Configuring phpmyadmin ├──┐
│ │
│ An error occurred while installing the database:
│
│
I am encountering the same issue in 20.04. The message is repeating
approximately every three seconds, resulting in log files of hundreds of
gigabytes. It also makes the system log nearly useless for any other
use; it is near-impossible to even open the file, and causes logrotate
to hang up for
Example of errors:
Jun 1 18:27:41 europa nm-applet[2158]: Can't set a parent on widget which has
a parent
Jun 1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion
'GTK_IS_WIDGET (widget)' failed
Jun 1 18:28:44 europa nm-applet[2158]: gtk_widget_destroy: assertion
'GTK_IS_WIDGET
1 - 100 of 1382 matches
Mail list logo
