I have mentioned this issue in the meta upstream bug:
- [meta] Repackage Thunderbird as a Snap package:
https://bugzilla.mozilla.org/show_bug.cgi?id=1498413
** Bug watch added: Mozilla Bugzilla #1498413
https://bugzilla.mozilla.org/show_bug.cgi?id=1498413
--
You received this bug notificatio
Public bug reported:
As mentioned in the changelogs, after upgrading Ubuntu from 22.04 LTS to
24.04 LTS, Thunderbird is now provided through snaps. Consequently, the
keepassxc-mail plugin (https://github.com/kkapsner/keepassxc-mail) has
stopped working due to issues with native messaging.
I have
Changing units helped. Thanks
** Changed in: gnome-system-monitor (Ubuntu)
Status: Incomplete => Invalid
** Information type changed from Public to Private
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in U
What is so difficult to read in the dump posted which clearly states
which description / version / release it is .. and that cups isnt
available nor that the websites referred to fail.
Expected result .. PRINTS
Actual result DOESNT PRINT
--
You received this bug notification because you a
Public bug reported:
Gnome System Monitor has been incorrectly showing the amount of RAM for
some time (months?). Based on the system logs, I was able to determine
that Gnome System Monitor has not been updated recently. So where is the
incorrect data coming from?
Gnome System Monitor:
RAM: 33.5
I am attaching the logs.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2000835/+attachment/5639364/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https:
*** This bug is a duplicate of bug 1970918 ***
https://bugs.launchpad.net/bugs/1970918
Probably a duplicate of https://bugs.launchpad.net/ubuntu/+source/tex-
common/+bug/1970918, which happened six months ago at my last ubuntu
upgrade
** This bug has been marked a duplicate of bug 1970918
Public bug reported:
Upgrade Ubuntu 22.04 to 22.10, same as 21.10 to 22.04, system seems to
get all the way through but there's an error with tex and the error
message implies that the entire system upgrade may have failed
ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: tex-common 6.17
Public bug reported:
Impact
--
This is a minor bugfix release of the 1.6.x series:
https://wpewebkit.org/release/wpebackend-fdo-1.6.1.html
The version currently in 20.04 LTS is 1.6.0, which accidentally shipped with
a bug that made the symbols wpe_fdo_get_{major,minor,micro}_version hidde
Public bug reported:
Performing Ubuntu upgrade from 21.10 to 22.04, tex-common upgrade fails
and "the upgrade is aborted and may have left your system in an unstable
state"
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: tex-common 6.17
ProcVersionSignature: Ubuntu 5.13.0-40.45-generic
So you can minimize this window and then have working Unity. If you
close it, your session ends.
This window belongs to a process of
/usr/libexec/gnome-session-failed
** Attachment added: "jammy-error-moved-aside.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1969357/+atta
Confirm (in KVM machines) that Unity works fine from gdm3 under Impish,
but a fresh VM of Jammy doesn't work with either lightdm or gdm for me.
I get to see a quick glimpse of the Unity desktop, then this fullscreen
splash error shows up
"Oh no! Something has gone wrong.
A problem has occurred a
Is this a `gnome-session` issue? The source sayeth (@ gnome-
session/main.c:422)
/* From 3.14 GDM sets XDG_CURRENT_DESKTOP. For compatibility with
* older versions of GDM, other display managers, and startx,
* set a fallback value if we don't find it set.
*/
Th
(In reply to Jeremy Bicha from comment #4)
> The first 2 did not work for me but the 3rd did.
>
> iris
>
> $ MESA_LOADER_DRIVER_OVERRIDE=iris yelp
> EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
> Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
> Unsupported modif
I don't compile WebKit w/ X11 support so I can't tell you if running
epiphany w/ GDK_BACKEND=x11 helps anything
---
I do not see those EGL errors when I run epiphany on the host. However,
if I run the Epiphany flatpak with FLATPAK_GL_DRIVERS=host, I get
EGLDisplay Initialization failed: EGL_BAD_
OK I found a way to fix it @ package time! I previously built webkitgtk
with -DENABLE_X11_TARGET=OFF. I tried building with
-DENABLE_X11_TARGET=ON (since this is the major difference between my
build and the gnome-build-meta build, aside from Mesa version), and now
it works properly
Seems like dis
Public bug reported:
Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio Realtek
ALC4080 is not recording audio. What I did found out, that the bar which
indicates that something is recording is going up, when I play some
sound on ubuntu, so input "thinks" it is output I think.
If ra
Public bug reported:
Problem:
Since the security updates on 2021-11-23 connecting my headset causes
bluetoothd to crash, which drops all the other connections.
Expected:
Headset connects and works as it has done previously.
❯ lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:
Hi, any sign that this issue is being looked at?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1913940
Title:
Wifi keeps disconnecting and reconnecting all the time
Status in wpa packag
Been running -460 for ages, my syslog occupies 80GB of disk space and
out of 526M log lines, 99.996% of them mention "Nautilus".
** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-460 (Ubuntu)
Status: New
Hi, any news on fixing this issue? If not, do you have any workaround I
could try at least?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1913940
Title:
Wifi keeps disconnecting and reco
Okay, ever since I installed this bug fix, my mouse has been playing up.
First, dragging and dropping across windows exhibited errant behaviour,
such as dropping the dragging item in between box borders. Now, every
once in a while, my mouse's primary buttons switch. The original issue
has been reso
@Marco thank you for your post regarding the test packages (comment
#50). This has almost solved the problem for me. I still get enlarged
text at the decryption password screen. Not a problem for me, but maybe
the information will help you guys.
--
You received this bug notification because you a
I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behavior. I am
fairly certain th
I did just want to add that it seems the update has affected the mouse
as well. Transitions between windows seems to occasionally disable the
mouse click momentarily. This is an issue in dragging and dropping,
which will occasionally cut out or display unpredictable behaviour. I am
fairly certain t
Thankyou Konrad, your comment #17, has solved this issue for me. I did
not hold the package at 6-0, though. Personal preference, but I feel
that accidentally updating and breaking it again is a simple fix, while
having a hold on a package that you have to remember to unhold could sit
in the backgro
Hello Akhil
Thankyou for this suggestion and the time you have put in. I tried this,
and a few other workarounds from a few other forums, and they have all
failed for me. The only solution has been to roll back the recently
updated 'libmutter' package, as per comment #17 in
https://bugs.launchpad.
0.walbert - where did you place these commands? I'm a little new to this
and I have been having the same problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1892521
Title:
UI bug -
Public bug reported:
Hello, I recently put together a new PC and installed a fresh Ubuntu
20.04. Immediately I noticed that, on startup, there was a flashing
cursor and the decryption password screen was unusually large, but the
login screen and desktop GUI was fine, so I thought nothing of it. Wi
Hi, Upgraded an old desktop from 19.10 to 20.04 and hit this graphics
display issue. I also have the same graphics card:
>From lspci:
03:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7600 GT]
(rev a1)
Is there any workaround I can perform to make this desktop usable? Other
th
This bug is still happening .. it really does render this whole
package unworkable .. its equivalent to the computer not working at
all. At least that way you know your data isn't being corrupted. I'm
appalled at the cavalier attitude this bug is being treated...other
end itus ... I ag
Incidentally this bug has been happening and someone suggested updating
Mutter to the latest version.
I had to install mutter to then update it to try and fix it .. so now
there are bugs due to software that was never installed in the first
place !!!
--
You received this bug notification beca
This is still happening despite the Ubuntu 20.04LTS installation being
fully patched using Liveupdate as at 25 May 2020.
In LibreOffice I have to hit Cntrl C repeatedly (more than 2 times or
click the copy icon sometimes 9 times or more to get some data and
this is just staying within Office
26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 2706 F pulseaudio
/dev/snd/pcmC0D0p: adrian 2706 F...m pulseaudio
/dev/snd/controlC1: adrian 2706 F
/controlC0: adrian 2706 F pulseaudio
/dev/snd/pcmC0D0p: adrian 2706 F...m pulseaudio
/dev/snd/controlC1: adrian 2706 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 10:13:38 2020
InstallationDate: Installed on 2018-05-20
amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 2706 F pulseaudio
/dev/snd/pcmC0D0p: adrian 2706 F...m pulseaudio
/dev/snd/controlC1: adrian 2706 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 29 10:
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 2706 F pulseaudio
/dev/snd/pcmC0D0p: adrian 2706 F...m pulseaudio
/dev/snd/controlC1: adrian 2706 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop
s
card 0: SI7012 [SiS SI7012], device 0: Intel ICH [SiS SI7012]
Subdevices: 0/1
Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: adrian 1332 F pulseaudio
adrian21093 F
** Description changed:
- The internal mic of my laptop is not working in Skype and doesn't show
- up under Input in the Sound settings.
+ The internal mic of my laptop is not working and doesn't show up under
+ Input in the Sound settings.
Internal speakers are working fine.
The microph
I had previously installed Gimp-Gutenprint as the driver for the
printer, via the control panel, and in fact going via Gimp File Print
gets a print, with the Gutenprint options in the "ordinary" print
dialogue. I'm not sure it is quite so good though, so far, and I don't
have the icc profile stuff
Removed and recreated printer. No change.
Removed plugins - not Gutenprint of coure - no change.
Starting gimp in a terminal with --verbose leads to
Initializing plug-in:
'/usr/lib/gimp/2.0/plug-ins/file-rawtherapee/file-rawtherapee'
Initializing plug-in: '/usr/lib/gimp/2.0/plug-ins/file-darkta
Public bug reported:
I use Gimp-gutenprint to print photographs via CUPS to an Epson R2400
It fails each time, reporting filter failure.
I forget what the last update was, yesterday or day before, but it is only
since then.
ESC/P utility can print a nozzle check from the printer, that's working.
** Attachment added: "list_devices"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281528/+files/list_devices
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
ht
Here are the logs:
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1839010/+attachment/5281525/+files/journal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in
Public bug reported:
I previously had Windows 10 on my protab laptop. After wiping the hard
drive and installing Ubuntu 19.04 on the device, the touchpad ceases to
respond at all. I am using an external mouse currently.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-control-center 1:
Public bug reported:
I recently installed Ubuntu 19.04 on this protab laptop. In the settings
menu the sound output shows a headphone and a multichannel output
option. There is no sound coming out of either system, despite there
being sound detection demonstrated in the sound bars in the output me
I finally posted on the pulseaudio list and someone referred me to this
bug:
https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/1793640
I uninstalled timidity and that seems to have fixed the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which
So is the next step that I should post this to pulseaudio-
disc...@lists.freedesktop.org? Do I need to be a list member to post
there?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs
On my ubuntu 18.04 system I only have
/usr/bin/pulseaudio --start --log-target=syslog
owned by me. On my 19.04 system
/usr/bin/pulseaudio --daemonize=no
also owned by me. Note gdm is not running. I assume lightdm, which is
running, is the alternative.
--
You received this bug notification
>From ps I see that "/usr/bin/pulseaudio --daemonize=no" is running with
user "adrian" and also my home directory is owned by "adrian".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in U
I already posted the log file a.txt in its entirety. Here it is again:
D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot access autospawn lock.
E:
I forgot to mention that dpkg -S says:
libpulse0:amd64, libpulse0:i386: /etc/pulse/client.conf.d/00-disable-
autospawn.conf
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828136
T
I looked around a bit and found ~/.config/pulse, a directory with
permission 700. Changed it to 777. That didn't make a difference.
Also found ~/.pulse with this contents:
12 -rw-r--r-- 1 adrian adrian 12288 Oct 7 2013
11597e2b32f1c4cb56501b9c0008-card-database.tdb
4 -rw-r--r-- 1 a
I removed the 00-disable-autospawn.conf file and rebooted. Then I get
a.txt containing this:
D: [pulseaudio] conf-parser.c: Parsing configuration file '/etc/pulse/client.con
f'
E: [autospawn] core-util.c: Home directory not accessible: Permission denied
W: [autospawn] lock-autospawn.c: Cannot acc
I believe that I upgraded incrementally as new releases came out from
14.04. (Hard to recall for sure back that far.) But definitely I got to
18.10 from 18.04 to 18.04 from 17.10. And 18.04, I didn't have this
problem. In fact, I have a second machine that I'm "scared" to upgrade
that's still ru
I followed the instructions but no log file was created.
I noticed in the man page for pulse-client.conf it says
extra-arguments= Extra arguments to pass to the PulseAudio daemon when
autospawning.
and in /etc/pulse/client.conf.d I see
autospan=no
I tried playing sound, running "alsa
The issue persists on 19.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1778011
Title:
SRU: PRIME Power Saving mode draws too much power
Status in HWE Next:
New
Status in
The before file was attached to the last comment. Here's the after file
from pactl.
** Attachment added: "postforce"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+attachment/5263010/+files/postforce
--
You received this bug notification because you are a member of Desk
I rebooted, ran pactl list cards, ran alsa force reload, then re-ran the
pactl command. Results was as you predicted. The pactl outputs before
and after appear below.
Here's the before output:
Card #0
Name: alsa_card.pci-_01_00.1
Driver: module-alsa-card.c
Owner Modu
I rebooted and went into the "Ubuntu" desktop and looked at the sound
settings. It shows an output tab and said "dummy". I clicked and was
able to switch it to the nvidia card. I think maybe the nvidia card was
off, which it should be since there's no output device connected.
I went back into m
If I look at the sound settings using pavucontrol (I don't normally use
gnome and don't seem to have a program called gnome-sound-setting
installed) then under the configuration tab I see the nvidia hardware
but not the built in audio. (The nvidia card has only HDMI and my
speakers don't have that
Summary: looks to me like aplay -l is showing the intel hardware. No
adrian> ls -la /dev/snd
total 0
0 drwxr-xr-x 3 root root 320 May 9 18:07 ./
0 drwxr-xr-x 20 root root 5080 May 9 18:07 ../
0 drwxr-xr-x 2 root root 80 May 9 18:07 by-path/
0 crw-rw+ 1 root audio
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262477/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262473/+files/CRDA.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1828
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262480/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262481/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262478/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https:/
I ran the "apport-collect 1828136" command as directed by the automated
script. A little puzzled that it gave the message
dpkg-query: no packages found matching alsa-driver
dpkg-query: no packages found matching linux
--
You received this bug notification because you are a member of Desktop
Pac
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262475/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/18
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262479/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.la
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262476/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/18
The automated script said I should change the status to "confirmed" even
though I am the reporter.
When 18.10 came out some other people reported similar issues:
https://ubuntuforums.org/showthread.php?t=2403077
https://ubuntuforums.org/showthread.php?t=2405764
--
You received this bug notific
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262482/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262472/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://b
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1828136/+attachment/5262474/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launch
apport information
** Tags added: apport-collected
** Description changed:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and persis
I repeat, immediately after a reboot, audacity is not running. Are you
saying that audacity can prevent the system from recognizing my sound
hardware at boot just from being installed?
At the moment, sound works despite the audacity's configuration because
I ran "alsa force-reload'.
--
You rece
I'm a little confused here. What does audacity have to do with the fact
that there is no sound after a reboot? Audacity happens to be running
now...perhaps that's why it's the only program using ALSA. (Is ALSA
deprecated?) But audacity does not start automatically at boot, so it
is irrelevant t
Public bug reported:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and persists now in 19.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package
Public bug reported:
As mentioned, after a lock-wake cycle, the wallpaper turns to pixel
garbage as seen on the screenshot.
Workaround: Setting the wallpaper from GNOME Tweaks, just not in the
same adjustment mode as before. For example, if the adjustment was set
to Zoom, now I must set it to som
Public bug reported:
Brightness level can't be changed from keyboard with the Fn key and the
corresponding designated key. Other functions like changing volumes
involving the Fn key work perfectly. The only way I can change
brightness is from the status bar.
Current OS: Ubuntu 19.04 Disco Dingo (
Public bug reported:
Before the screen when you enter the password, where the clock is shown,
if a key is pressed, it does not retract the screen upwards, as it used
to. Now I have to manually use my mouse to drag the screen up. Not sure
if it is the way it was intended to be used, but I am submit
Public bug reported:
In place of the login background I chose, I either see a white scree, or
what appears to be random pixels, with the normal clock on top.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Lin
After seeing Alex's post, I tried installing 410.104-0ubuntu0~18.10.1 from
ppa:graphics-drivers.
Using 4.18.0-16-generic kernel.
I find that when I use Intel profile, powertop reports the nvidia card as 0%
active, and the setting in Tunables shows up as Good.
However, /proc/acpi/bbswitch reports
> * If I understand correctly, the bug does not occur in Ubuntu 18.10.
The user can switch seamlessly between using the Intel or the Nvidia
discrete graphics card. Is this correct?
@jespestana
No, this bug is affecting me on 18.10.
--
You received this bug notification because you are a member o
I am facing the same issue in Ubuntu 18.10. The super key randomly stops
working and I loose control of all windows except for the active window,
which in some cases also stops working and cannot even do clicks there.
The workaround I found is to close all windows, lock the screen and the
problem s
I can confirm that installing nvidia-390 through the Ubuntu driver dialog, and
then using nvidia-settings or prime-select to set intel keeps the nvidia card
on for me on my GeForce 840M laptop.
I can also confirm Installing bbswitch-dkms and turning it off through bbswitch
works.
--
You receiv
Public bug reported:
No sound from headphones from ubuntu desktop.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd6
I have the same problem. I have /home in a separated filesystem, and
every time a wakeup my lap this ext4 partition is mounted as ro.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/9016
So I became somewhat frustrated by this issue and used new installation
media to completely reinstall ubuntu 18.04, removing the old partition and
starting again from scratch. I installed steam as soon as the
re-installation process had been completed, and downloaded/played Kerbal
Space Program. I
Just to add, this is the screenshot I took of another attempt. The upgrade
commands are there just to show what I see when I run those commands. They
were run previous to a reboot, then I ran them again to make the screenshot.
Regards, Adrian
On Tue, 23 Oct 2018 at 21:15, Adrian Barbuio
wrote
Okay, so I have run the update and reboot commands. I tried to run the
ubuntu-bug command again and I got exactly the same error message as was in
the previous screenshot.
On Tue, 23 Oct 2018 at 20:46, Daniel van Vugt
wrote:
> That screenshot shows that you can't report crash files because your
I have no
extensions installed?
Regards, Adrian
On Tue, 23 Oct 2018 at 19:11, Daniel van Vugt
wrote:
> Thanks. It looks like something is crashing at the end (where you see
> "whoopsie") but I can't yet tell what.
>
> Firstly, please remove/disable all gnome-shell extens
Hello Daniel. I have performed the tasks you requested and have the
relevant text file attached.
Regards, Adrian
On 23/10/18 4:43 pm, Daniel van Vugt wrote:
> Please:
>
> 1. Reboot and run nothing other than one game that will trigger the bug.
> Do not run any other apps.
>
>
Hello Daniel
I did not receive any instructions, or any text at all in your last
message. I am just wanting to know if there is any update on this issue
and how to solve it.
Regards, Adrian
On 22/10/18 6:22 pm, Daniel van Vugt wrote:
> ** Also affects: xserver-xorg-video-amdgpu (Ubu
No worries. The txt file is attached.
Regards, Adrian
On 22/10/18 5:28 pm, Daniel van Vugt wrote:
> Thanks.
>
> Please also run this command and send us the output:
>
>dpkg -l > allpackages.txt
>
> ** Summary changed:
>
> - All video games freeze 5-10mins in
Public bug reported:
I recently installed steam on my system (Ubuntu 18.04), installed a
couple of games and attemped to play them. About a couple of minutes in
to playing cities: skylines, kerbal space program and mount and blade:
warband, the screen goes blank and the computer freezes. A hard re
It worked like a charme. Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1797945
Title:
Lightning incompatible with Thunderbird 60.2.1
Status in thunderbird package in
Where do I put the .xpi file to be recognized by Thunderbird?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1797945
Title:
Lightning incompatible with Thunderbird 60.2.1
Status
** Bug watch added: github.com/alcinnz/Odysseus/issues #147
https://github.com/alcinnz/Odysseus/issues/147
** Also affects: webkit-open-source via
https://github.com/alcinnz/Odysseus/issues/147
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
1 - 100 of 457 matches
Mail list logo
