Public bug reported:
I have a local APT repository with a non-lowercase suite identifier.
apt-add-repository always forces it into lowercase, which causes apt to
emit warnings when it notices the mismatch:
$ sudo apt-add-repository "deb http://example.com/deb FooBar Baz"
Repository: 'deb
Public bug reported:
using integrated intel gpu no nvidia
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog:
Public bug reported:
consistently fails to resume from suspend
using integrated intel gpu no nvidia
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion:
According to the launchpad page for mesa 22.2.5-0ubuntu0.1~22.04.2
(https://launchpad.net/ubuntu/+source/mesa/22.2.5-0ubuntu0.1~22.04.2)
the package is still in proposed, not updates. @tjaalton 's message in
#72 suggests it has been released to updates but this appears incorrect.
I'm on 22.04
Also, forgive me as I'm a n00b with using Launchpad. I was not sure how
to add the tag "verification-failed-lunar". Thanks.
--
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/2013216
Title:
I was able easily to install version 44.1 as well:
$ sudo apt-get install mutter/lunar-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '44.1-0ubuntu1' (Ubuntu:23.04/lunar-proposed [amd64]) for
'mutter'
Selected version
Super, thank you for the information, Jeremy.
-SW
On Tue, May 23, 2023 at 3:55 PM Jeremy Bícha <2013...@bugs.launchpad.net>
wrote:
> Scott, the mutter 44.1 update for Ubuntu 23.04 needs to be manually
> approved by a member of the Ubuntu SRU team before it will be built as a
> -
Is there any news or ETA for the new mutter 44.1-1ubuntu1 package?
--
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/2013216
Title:
Single click on title bar does not transfer focus to
Is there any specific date that Gnome 44.1 will be released for Lunar?
Also, FYI only, I've noticed that Firefox (snap, version 112.0.2-1, rev
2605) doesn't seem to suffer the same issue as other application
windows. I wonder why that is?
--
You received this bug notification because you are a
Additional info, not sure if it has any relivance but the last update
installed a new wi fi driver for RTL8821CE card. It seemed to take a
very long time to install.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
Yesterday Toshiba M300 laptop ran for around 5mins. Screen went black and
flashing cursor in top corner then stopped and started again with log in
screen. As duel boot started laptop in Windows 10 and no problems so software
problem. Reseached and found a fix which was
I tried the lines:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment as suggested.
It does not help. Or it did not help much. I think the keyboard lag might be
less prevalent, but the mouse is still problematic.
My symptoms remain the same:
1.
I tried the lines:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
in /etc/environment as suggested.
It does not help. Or it did not help much. I think the keyboard lag might be
less prevalent, but the mouse is still problematic.
My symptoms remain the same:
1.
Public bug reported:
SYSTEM INFORMATION:
user@host# lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
PACKAGE VERSION INFORMATION:
user@host# apt-cache policy ubuntu-drivers-common
ubuntu-drivers-common:
Installed: 1:0.9.6.1
Candidate: 1:0.9.6.1
Version table:
***
I am observing the same issue on 22.04. I cannot drag and drop from
nautilus into chrome or slack.
If I switch to an xorg session I can drag and drop.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1967812
Title:
ubuntu 22.04 beta crash regarding gnome-shell and several others
This issue was fixed in https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/994 which avoids changing `xkb-options` unless
the Alternate Characters dialog is opened. (That was originally part of
MR 910, but was split off so it could be merged without being blocked on
design
It happened to me too
** Attachment added: "Crash log of amdgpu driver"
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5516220/+files/amdgu_crash.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Error on nvidia 340 install. Computer freezes while using Google Chrome.
Chromium did not work at all. Kubuntu 20.10 Beta release with all
updates. When trying to install 340 is below.
Unpacking nvidia-opencl-icd-340 (340.108-0ubuntu5) ...
Selecting previously unselected package
Public bug reported:
After playing sound for a while (minutes, not seconds), the right
channel will become attenuated.
Restoring balance can be done by unplugging the headphones (from the
built-in sound card) or disconnecting the external DAC and reconnecting
it.
Balance can be restored by
apport information
** Attachment added: "NvidiaBugReportLog.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408777/+files/NvidiaBugReportLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408776/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408784/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408783/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408789/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "nvidia-settings.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408788/+files/nvidia-settings.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408787/+files/acpidump.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408785/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408786/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408782/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408781/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408780/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408779/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408778/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408770/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408775/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408771/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408774/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1894852
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408773/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1894852/+attachment/5408772/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1894852
apport information
** Tags added: apport-collected has-workaround reproducible single-
occurrence ubuntu
** Description changed:
I selected the nvidia driver as I did not know which package to select.
I am pretty sure that is not the problem as that driver is supposed to
support the
#63 and #65 did not work for me, resulted in dummy audio - #66 also did
not work for me.
--
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/1840725
Title:
Microphone not working in
for #78 my specs
Linux michaelroelker-Lenovo-YOGA-C930-13IKB 5.4.0-39-generic #43-Ubuntu
SMP Fri Jun 19 10:28:31 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC298 Analog [ALC298 Analog]
Subdevices: 1/1
Subdevice
*** This bug is a duplicate of bug 1869561 ***
https://bugs.launchpad.net/bugs/1869561
Public bug reported:
When trying to get help in LibreOffice Writer it is unavailable. See
attachment for exact dialog. I have uninstalled and reinstalled the
package libreoffice-help-en-us and it doesn't
this worked for me to set all profiles as I wanted in 20.04
$ val='@ms
Happens to me (headset recognized but no sound) XPS 13 9380
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1866194
Title:
External audio device shows up in the sound
i got an email about released. I also notice on here that a fix has been
released. I don't see it as an update via software updates. How to I get
the fix.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
The power button in gdm3 will not power off or reboot the system.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset
I can confirm that I am still having this issue on 3.34 as well
(Manjaro).
This is shocking to me that anyone using Gnome to develop doesn't
encounter this bug at minimum of 5x per day. Or are Gnome developers
using MacOS and MBPs to develop like those in the lol "Linux"
Foundation
Public bug reported:
Image: 19.10 beta –
http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso
Device: Dell Precision 5540 (201904-26937)
1. Install Ubuntu 19.10.
2. Check 'Encrypt the new Ubuntu Installation for security' and 'Use LVM with
the new Ubuntu Installation'
3.
The problem should be fixed in git, and available in the 1.14.0.
I don't think there's a workaround other than building from source; but it
should be possible to address it that way.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
For those that run linux and want to update their Firefox icon so it
automatically launches with GTK_THEME="Adwaita:light" firefox %u instead
(band-aid work around that shouldn't need to be).
$ cp /usr/share/applications/firefox.desktop ~/.local/share/applications
$ gedit
I am having this issue with Firefox 66.0.3 using Ubuntu 19.04 (Gnome
3.32 using Adwaita dark).
This release seems to ignore:
widget.content.allow-gtk-dark-theme in about:config is set to default / false
widget.chrome.allow-gtk-dark-theme in about:config is also default /false
I came back to
I believe I made a mistake in the steps taken above.
I believe I rebooted my computer once after the `journalctl --vacuum-
time=1s`
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
# journalctl rotate
# journalctl --vacuum-time=1s
journalctl -b-1 --no-pager > prevboot.txt
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828649/+attachment/5264569/+files/prevboot.txt
--
You received this bug notification because you
Public bug reported:
When I switch to wayland the gnome desktop locks up before I see my desktop.
It doesn't lock up when I have my laptop closed and only one display connected.
When I connect up the second display, it locks up every time.
I tried deleting my monitors.xml file.. that doesn't
I had a similar issue with my HP Spectre laptop, and submitted a bug to
libinput: https://gitlab.freedesktop.org/libinput/libinput/issues/261
So with libinput, it seems this can be addressed with the
"ModelTabletNoProximityOut" quirk; though libinput needs a more general
solution to not require
Public bug reported:
Not able to get GUI mode in ubuntu 18.04 ... 16.04 was fine
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
NonfreeKernelModules: edac_mce_amd wmi_bmof
WORKAROUND on how to use keyboard Ctrl+Shift+/Alf+Shift+ shortcuts with
Ctrl+Shift as layout switch.
Order of keys pressed for layout switching is important. So
['Shift_L'] implies Control pressed first and Shift pressed
second. Inverse order won't work. You have to use ['Control_L']
for inverse
** Changed in: gvfs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1815395
Title:
GVFS-SMB write problems to SMB2 shares
Status in gvfs package
I can into this when using the following:
$ apt list --installed gnome-shell xorg ibus
gnome-shell/cosmic-updates,now 3.30.1-2ubuntu1.18.10.2 amd64 [installed]
ibus/cosmic,now 1.5.19-1ubuntu1 amd64 [installed]
xorg/cosmic,now 1:7.7+19ubuntu8 amd64 [installed]
On Thu, 21 Feb 2019, 14:30 Olivier
Also, I have no customizations to the OS generally. I am using the OS
video driver for amd.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1801494
Title:
I'm now seeing this issue, after messing with my monitor cables. I only
have a single monitor. I was trying to get my DVI to work on my AMD
RX550 card - which will not display while logged in (but does at bios).
Both cables are currently plugged into the same monitor (diff ports of
course) in
cause the problem to
recur.
I suppose this is why I wanted to see if anyone could replicate this. I
would bet now that they couldn't but I doubt I'll ever know what the
actual issue was, now.
Anyway, I'm closing this bug. Sorry for the false alarm. :)
Thanks,
Scott
--
You received thi
Sorry, spoke too soon. I'm not sure which status to change this to. It
was never confirmed by anyone else, but the traces definitely showed
something bad happening. Any suggestions what I should set the status
to in order to properly file it away?
--
You received this bug notification because
Will do. I wanted to post here before cross-posting it in case the
issue was something to do with the Ubuntu implementation of GVFS and not
GVFS itself. I was also kind of hoping someone could do my tests to
confirm this is actually a bug and not some craziness that only affects
me but I suppose
Public bug reported:
Summary:
I believe there’s a bug in GVFS-SMB (or its implementation in Nautilus)
that manifests when writing to SMB2 shares. It occurs inconsistently
(but enough to be annoying) in everyday use, but it can be replicated
consistently with a simple echo command redirected to
The solution until this is solved is to use something other than gnome
shell as far as I know. Mint Cinnamon and Elementary are both popular
alternatives.
On Sun, Feb 10, 2019, 1:29 PM Adrian <1181...@bugs.launchpad.net wrote:
> I am facing the same issue in Ubuntu 18.10. The super key randomly
After testing from a well modified system, the issue appears after I
install the amdgpu driver from AMD.
THAT SAID, this issue is noticeable on videos that I have viewed on this
system since initial install in January. I constantly view many videos
in Videos (every day) - so I suspect that
example of good video properties
** Attachment added: "example of good video properties"
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5235705/+files/Selection_183.png
--
You received this bug notification because you are a member of Desktop
Packages,
example of broken video properties
** Attachment added: "example of broken video properties"
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5235704/+files/Selection_182.png
--
You received this bug notification because you are a member of Desktop
I'm experiencing this issue as well. I have an RX550 video card, using
Ubuntu's drivers.
Has anyone reported this to mesa, and if so where? If someone can share
the right location/component for ME to log a bug, I will do so.
It seems that AMD GPUs are quite useless today, a million things are
Same very high CPU on Ubuntu 19.04 just
after I installed, launched and logged into gmail
using browser chrome Version 73.0.3679.0 (Official Build) dev (64-bit)
After 5 mins
/usr/bin/gnome-keyring-daemon --daemonize --login
no longer used high CPU
--
You received this bug notification
For my reference later.
The 'dconf read' with ':list' syntax has changed, so the comments above don't
work in 18.04.
Updated, this worked for me:
$ dconf list /org/gnome/terminal/legacy/profiles:/
:b1dcc9dd-5262-4d8d-a863-c897e6d979b9/
$ dconf write
Public bug reported:
In xenial the file
/usr/lib/x86_64-linux-gnu/librsvg-2.a
was still there but in bionic onwards it's missing. I cannot statically
link with librsvg-2 without it. Please add it back in.
** Affects: librsvg (Ubuntu)
Importance: Undecided
Status: New
--
*** This bug is a duplicate of bug 1735071 ***
https://bugs.launchpad.net/bugs/1735071
** This bug has been marked a duplicate of bug 1735071
Ctrl + F search disengages immediately after CTRL + F pressed
--
You received this bug notification because you are a member of Desktop
Packages,
*** This bug is a duplicate of bug 1735071 ***
https://bugs.launchpad.net/bugs/1735071
** This bug is no longer a duplicate of bug 1801912
ctrl-f doesn't open the search box
** This bug has been marked a duplicate of bug 1735071
Ctrl + F search disengages immediately after CTRL + F
** This bug is no longer a duplicate of bug 1801912
ctrl-f doesn't open the search box
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1735071
Title:
Ctrl + F search
Well, I think I found out what was happening.
In gnome-tweaks I had somehow gotten 'Workspaces' -> 'Display Handling'
set to 'Workspaces on primary display only'.
So what happened was that there was only a single workspace on the
"second" head and thus no need for "always on visible workspace".
Yes I have a password ... wrt #1803527 I removed all gnome extensions no
help.
UPDATE - this issue only happens when using nvidia drivers installed
using Software & Updates -> Additional Drivers -> nvidia 390 , with
nouveau its OK
** Description changed:
This is not a problem using only
ubuntu13.1
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: scott 2102 F pulseaudio
BuildID: 20181116130029
Channel: Unavailable
CurrentDesktop: LXQt
Date: Sun Dec 2 10:07:40 2018
ExecutablePath: /usr/lib/firefox/plugin-container
Extensions: extensions.sqli
** Description changed:
This is not a problem using only built in laptop screen however when I
attach an external monitor and choose
Setting->Display->Single Display
then choose the external monitor to be the only active screen -> then
when I suspend upon resume the external
Public bug reported:
This is not a problem using only built in laptop screen however when I
attach an external monitor and choose
Setting->Display->Single Display
then choose the external monitor to be the only active screen -> then
when I suspend upon resume the external monitor lights up
I just now realized that this issue only occurs when the window is on my
"second" monitor.
If move the window to the primary display then the window menu has
Minimize, Maximize, Move, Resize, Always on Top, Always on Visible
Workspace, Move Workspace Down, Move to Monitor Right, Close
But on
Thanks Olivier.
A little lagniappe for me. My Enpass plugin had quit working about 6 months
ago. Tried a bunch of stuff but could never get it to work. It's working now!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in
Yes, right after the upgrade here too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1798999
Title:
firefox windows are black in Ubuntu 18.10
Status in firefox package in Ubuntu:
Yes, that also worked for me. I never enabled it myself, so something
may have went awry during the upgrade. I didn't do a clean install if
that helps.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Happening to me also. Intel graphics. I've removed everything and reinstalled
it. Same.
But the Firefox Snap works fine. So do Chromium and Opera.
Only since the upgrade to 18.10 64bit
code
[GFX1-]: Failed to lock new back buffer.
[Parent 2199, Main Thread] WARNING: failed to open shm:
Don't get too excited..
https://gitlab.gnome.org/GNOME/nautilus/issues/703
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1706097
Title:
gvfsd-mtp crashed with SIGSEGV
Status in gvfs:
** Attachment added: "the horizontal band"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203629/+files/20181020_172736.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
** Attachment added: "the bright box"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799061/+attachment/5203630/+files/20181020_172739.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Also note that the screen jitters at the GDM login screen.
My video card does not exhibit have any of these issues when I boot into
Windows 10.
Sometimes logging in doesn't fix the jittering so I reboot into Windows
10.
--
You received this bug notification because you are a member of Desktop
Public bug reported:
Video does not appear to be getting set correctly for GDM but seems
"corrected" after I login.
I have attached some screenshots.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux
Public bug reported:
I filed bug 1795410 a few weeks ago complaining that the 'alt space'
didn't bring up the window menu. That is now fixed (seemingly likely
with mutter 3.3.0-6).
However, the window menu that does come up does not have an entry for
'Always on visible workspace' as it used to.
Well, after an upgrade and reboot (including mutter 3.30.1-1), 'alt
space' now works to bring up the m enu.
However, there is no 'Always on visible workspace' option.
So I will close this bug as 'fix released' and I have opened bug
1797120.
** Changed in: mutter (Ubuntu)
Status: New =>
As a work around, I just configured some short cut (super w) to 'Toggle
window on all workspaces or one' in the gnome-control-center and that
seems to function.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Sorry to necro such an old thread but there seems to be a regression. I
have this same issue on my Lenovo Ideapad 320s. Given that it seems
almost unique to Lenovo, would it be possible to create a general case
for all Lenovo laptops where muting one internal microphone is an option
by default?
I ran sudo apt-get autoclean, and other command line clean up tools and
tried again.
I was able to upgrade then. Not sure why just running some cleaning
programs worked but did and now I have 18.10 running.
Thank you
You can marked this solved.
Scott Stehno
On 09/25/2018 08:46 AM, Colin
Everything I have read points to the "3D Driveguard". I appreciate the feature
and would not so much mind the screen auto-reorientation both
a) the screen orientation would auto reset even when the screen is locked
b) screen auto-reorientation could be controlled or disabled in the system
I'm finding the same symptoms from gnome-shell, relatively high cpu use by
gnome-shell with all extenstions deisabled (if I turn on extensions the cpu
usages is ridiculous high, in the range of 20-50%).
I checked strace as above and am finding the same high number of errors from
the recvmsg
1 - 100 of 1831 matches
Mail list logo
