Public bug reported:
When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is
modified, the GNOME Shell theme remains in the default state, i.e. it
switches between light and dark together with the ‘Dark Style’ toggle.
It is impossible to set the Shell theme to be unconditionally dark
The same is here
Ubuntu 22.04.1 LTS
--
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/1868332
Title:
Scrolling jumps after switching windows
Status in mutter package in Ubuntu:
Confir
Public bug reported:
spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
default connected 1920x1080+0+0 0mm x 0mm
1920x1080 77.0*
Display setup
GDBus.Error:org.fre
The bug is reproduced on Eclipse IDE (screenshot
https://disk.yandex.ru/i/z7kqQV47z8xeFQ). Left click always closes the
popup window instead of set focus on it. Pressing the "F2" buttons leads
to the same result.
Ubuntu 20.04.3 LTS
GNOME Shell 3.36.9
Eclipse 2021-12 (4.22.0)
--
You received this
the same problem on 21.10
pulseaudio package 1:15.0+dfsg1-1ubuntu2
default output is reset in random order after resume from sleep.
Sometimes it stays as it was before suspend, but more often it just
changes to HDMI or dock output.
--
You received this bug notification because you are a member
Was this patch sent to the maintainers? If so, was it applied?
--
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/1870597
Title:
libinput says "your system is too slow"
Status in GNOME Sh
I can also confirm that update with hirsute-proposed enabled solves the problem
for me.
Before this, the problem used to be readily reproduced by the procedure
described in comment #51.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gn
I've found this forum thread:
https://forums.developer.nvidia.com/t/solus-nvidia-gtx-1070-brightness-
control-not-working/54472
If I understand correctly, the OP resolved his issue by setting the
kernel boot parameter
nvidia.NVreg_EnableBacklightHandler=1
This did not solve the issue for me
The built-in extensions (Desktop Icons, Ubuntu AppIndicators, Ubuntu Dock) can
be deactivated using the Extensions app.
Is it enough to close the issue?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Sorry, I changed the issue's type accidently.
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1849346
Title:
[snap]
This problem still persist and SPNEGO won't work even with new policies:
https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthServerAllowlist
https://cloud.google.com/docs/chrome-enterprise/policies/?policy=AuthNegotiateDelegateAllowlist
The policies are loaded successfully but k
The bug is solved
We need to create folder mkdir -p /etc/chromium-browser/policies/managed
manually and then browsre check the policies successfully
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bug
Hello!
This bug still persist in Chromium 87.0.4280.66 (Official Build) snap (64-bit)
Ubuntu 20.10
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1414753
Title:
Chromium brow
To add to my point 2: the same effect happens when using `pdftocairo` in
command line, so maybe the current issue is not about Evince.
It remains the problem with annotations created in Evince that just
disappear on printing.
--
You received this bug notification because you are a member of Desk
In fact, there seem to be multiple issues with printing annotations (at
least text highlighting).
This is about Evince 3.36.7 and Okular 20.08.2.
1. If a highlighting annotation is created in Evince, it is visible when
the file is opened with Evince, Okular, or Xournal++, but it disappears
on pri
I've tested ubuntu kernel 5.4.0-26-generic + debian packages (full os
install). It works fine. I can conclude this not kernel issue but
X-server or amd drivers.
Debian packages which works:
ii x11-xserver-utils7.7+8
amd64X server utiliti
** Tags added: focal groovy
--
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/1727321
Title:
drag and drop through the side panel to activate the window is not
Public bug reported:
Hello!
Rune Classic hungs OS on exit (music plays, but X or keyboard caps lock
not responding), Debian 10 works fine.
https://www.gog.com/game/rune_classic
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xserver-xorg-video-amdgpu 19.1.0-1
ProcVersionSignature: Ubuntu
Just deleted 240G syslog file after system stalled.
Syslog.1 is 20G full of folowing:
Aug 19 08:24:41 alexey-ASUS io.elementary.wingpanel.desktop[1935]:
[7f6cd43aa790] vdpau_chroma filter error: video mixer rendering failure: An
invalid handle value was provided.
Aug 19 08:24:41 alexey-ASUS
For now I can send udev event instead of replugging:
ls -l /sys/class/hidraw/ | grep :1050: | awk -F/ '{print $NF}' | xargs
-r -L1 -I T udevadm trigger -c add --name-match=T
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browse
Hm, now I updated chrome to 84.0.4147.105 (1260) and can reproduce it
reliably by inserting yubikey and then starting chromium with new
profile (chromium --user-data-dir=./111).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-bro
Sorry for long delay. No I can't reproduce it anymore in a way I described
before, but it still happens to me. For now certain is that repluging yubikey
fixes the problem, reboot doesn't.
Upgrading the snap most probably triggering it, need to test it more times.
--
You received this bug notifi
Funny thing. I have Yubikey 5C Nano and it is hard to get out of port.
So I plugged spare Yubikey 4 to get dmesg lines and it worked with
chromium. Then I replugged my yubikey 5c nano and it worked too. Then I
rebooted without unplugging yubikey and it not working in chromium again
but works in fir
name: chromium
summary: Chromium web browser, open-source version of Chrome
publisher: Canonical*
contact:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
license: unset
description: |
An open-source browser project that aims to build a safer, faster, a
Still not working. And right link to test is https://demo.yubico.com
/webauthn-technical/registration
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubike
This option does exist in Ubuntu Dock. It's just disabled by default. It can be
activated using Dconf Editor. Set the parameter
'org.gnome.shell.extensions.dash-to-dock' to be equal to 'cycle-windows'.
It can also be easily done by running this command:
gsettings set org.gnome.shell.extensions.d
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped working in chromiu
Log attached. Relevant line probably
[92777:92906:0709/115647.054273:ERROR:udev_watcher.cc(96)] Failed to
begin udev enumeration.
** Attachment added: "chrom3.log"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+attachment/5390970/+files/chrom3.log
--
You received t
Same here: Ubuntu 16.04.6 LTS.
--
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/1885159
Title:
Firefox after update doesn't start - Ubuntu 16.04.6 LTS
Status in firefox package in Ubun
Tested firefox snap - u2f works.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1884759
Title:
U2f yubikey stopped working in chromium snap
Status in chromium-browser packag
I use it only for github, no special setup was needed (udev rules are
already there for PIV). I logged last time some months ago so I don't
know when it stopped working exactly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-bro
It fixes the issue for me after update of gnome-shell package with
focal-proposed enabled.
gnome-shell version is 3.36.3-1ubuntu1~20.04.2
Tested using winecfg.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are
Public bug reported:
I was previously using u2f from yubikey in chromium snap, but now it doesn't
work.
No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced.
U2f still works in firefox installed as deb.
# snap connections chromium | grep u2f
u2f-devices chromium
I have updated yaru-theme from focal-proposed.
I confirm that together with gnome-shell-extension-ubuntu-dock previously
updated from proposed this fixes the issue for me in focal.
gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1)
yaru-theme (20.04.7)
Many thanks to everyone involved!
** Ta
I have updated gnome-shell-extension-ubuntu-dock from focal-proposed and it
doesn't fix the issue for me at the moment. I can guess that this is because
yaru-theme is not yet updated in focal-proposed.
gnome-shell-extension-ubuntu-dock (68ubuntu1~20.04.1)
yaru-theme-gnome-shell (20.04.6)
** Tags
I confirm that the issue is fixed for me in groovy.
gnome-shell-extension-ubuntu-dock (68ubuntu1)
yaru-theme-gnome-shell (20.10.1)
--
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.l
tarantula!root# ps axu | grep chr
root 561745 0.0 0.0 6436 728 pts/2S+ 15:20 0:00 grep chr
tarantula!root# snap refresh chromium
error: cannot refresh "chromium": snap "chromium" has running apps (chromium)
Had to restart snapd to update chromium snap.
--
You received this b
tarantula!root# snap refresh
core18 20200427 from Canonical✓ refreshed
tarantula!root# snap refresh
All snaps up to date.
tarantula!root# snap list | grep chromium
chromium 81.0.4044.1221119 latest/stable canonical*-
tarantula!root# snap info --abs-time chromium
name: c
tarantula!root# snap refresh
All snaps up to date.
How do I get the "latest" ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1864901
Title:
[snap] suggestion: alert users w
I'm still seeing the problem.
tarantula!root# snap refresh
All snaps up to date.
tarantula!root# snap list | grep chromium
chromium 81.0.4044.1221119 latest/stable canonical*-
--
You received this bug notification because you are a member of Desktop
Packages, which is subsc
*** This bug is a duplicate of bug 1843182 ***
https://bugs.launchpad.net/bugs/1843182
I have the same problem, I have grouped all applications into categories.
To reproduce the error, I open the category after clicking + and so on several
times until it freezes.
--
You received this bug no
*** This bug is a duplicate of bug 1843182 ***
https://bugs.launchpad.net/bugs/1843182
Sorry, not the + key, but the key Esc
--
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/18722
(In reply to Dennis Mayr from comment #53)
Ubuntu LTS has special policy for some programs (e.g. Firefox) to
upgrade them. I'm using Ubuntu 16.04 and have latest stable Firefox. So
this is not a problem.
> What other workarounds are available in a shorter timeframe?
https://bugzilla.mozilla.org/
I just found the issue second ago. It is related to SNAP_REEXEC
behavior. The idea is to run snap from snap_core installed from snap. If
you have system snap installed it will be reexec'd from snap core. To
disable it you need to change the source.
Just run this before compilation and you will be
Seems like a new linux virus preventing me from running compiled snap.
Not the right place to report but who knows? When I recompile the snap
package and changed "help" output to "refresh !!! and remove snaps" and
unpack the content of resulting file into 123/. I reinstall the system
package and re
For some reason I unable to rebuild snapd following #29 instruction. All
goes fine, but in the end xdg-open wont work. I've checked
/var/log/syslog and it full of:
chromium_chromium.desktop[1674]: user-open error: Supplied URL scheme
"magnet" is not allowed
What is interesting, when I'm changing
*** This bug is a duplicate of bug 1849859 ***
https://bugs.launchpad.net/bugs/1849859
I have the same issue on two PCs with HP LaserJet 1020 printer connected
to the Wi-Fi router on Ubuntu 19.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is su
I confirm this bug is still present in ubuntu 19.10.
My comment in gnome bug tracker: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1154#note_696130
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1154
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1154
--
You received
** Changed in: chromium-browser (Ubuntu)
Status: Fix Committed => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1837746
Title:
[snap] wrapper script doesn't sourc
I have put CHROMIUM_FLAGS="--force-device-scale-factor=2.0 --new-window"
in ~/.chromium-browser.init as I did before. But multiple options is not
parsed correctly as it was. I getting error:
"[18384:18384:/111220.448169:ERROR:display.cc(55)] Failed to parse
the default device scale factor:2 --n
snap disconnect chromium:chromium-config
snap connect chromium:chromium-config
This is resolved my issue
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1837746
Title:
[snap]
# dmesg | grep chromium-browser.init
[803454.414690] audit: type=1400 audit(1572333616.781:52868): apparmor="DENIED"
operation="open" profile="snap.chromium.chromium"
name="/home/baz/.chromium-browser.init" pid=5334 comm="chromium.launch"
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
$ ls -l ~/.chromium-browser.init
-rw-r--r-- 1 baz baz 60 мар 16 2018 /home/baz/.chromium-browser.init
$ snap connections chromium | grep personal-files
personal-fileschromium:chromium-config :personal-files
-
--
You received this bug notification because y
Chromium snap refuses to start if file exists:
$ chromium
/snap/chromium/917/bin/chromium.launcher: 78: .: Can't open
/home/baz/.chromium-browser.init
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://b
Hello!
The problem is still here. In 17.10, 18.04, 18.10, 19.04 releases...
I found out that all standard layout switches are with that stupid delay.
But somehow the alternative switching on LShift+RShift works instantly!
I spent few hours to find the place where this action is stored to move
i
Someone should revert this 'Fix Released' status - it is here again in
18.04 (and according to forums in 17.x also).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/36812
Title:
Ke
Public bug reported:
budgie-wm overclock when playing video in browser or instant player
nvidia 390, profile intel
similar to
https://discourse.ubuntubudgie.org/t/19-04-budgie-wm-constant-cpu-load-after-changing-scale/1879/15
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mutter 3.28.3+gi
There is no 3.28.4 release yet: https://gitlab.gnome.org/GNOME/gnome-
shell/tags
--
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/1774957
Title:
Network icons in status menu disappe
This bug affect me too - can't enter correct password in gnome-
screensaver. I'm using lightdm for login, if it matters
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1796888
Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install
and applying nvidia-390
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails to boot gra
Hm, after checking out the links Daniels provided, I am wondering if
this is not a duplicate or a different manifestation of bug #1774957...
I think I will not open a new upstream bug but will sign up to the
existing one: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140
--
You received this
Ok, thanks for the links to upstream bugs.
Julian, I propose the following title for GNOME bug report:
"WiFi/network icon and settings randomly disappear or misbehave in
status menu"
One more thing: I forgot to mention that I seem to observe the problem
randomly on roughly 1/2 of boots or logins
In fact, the issue is not limited to wireless networks. The wired
connection options are also not displayed correctly. This screenshot
shows what I see in the menu when connected to wired network with wrong
profile.
By the way, after I reinstalled Ubuntu 18.04.1, the problem showed up
for the fi
In fact, the issue is not limited to wireless networks. The wired
connection options are also not displayed correctly. This screenshot
shows what I see in the menu when connected to wired network with wrong
profile.
By the way, after I reinstalled Ubuntu 18.04.1, the problem showed up
for the fi
I think I am experiencing the same bug. Here is a screenshot of my
desktop with user menu when I am connected by WiFi.
By the way, I reinstalled Ubuntu 18.04.1 from scratch last week, but I
kept my user directory intact. I had this issue since upgrading to
18.04 from 17.10.
** Attachment added:
I have a similar issue. I'm trying to get the mic working on Beats X
headset. These series of patches helped me to solve the issue:
https://patchwork.freedesktop.org/patch/178198/
https://patchwork.freedesktop.org/patch/178199/
https://patchwork.freedesktop.org/patch/178200/
https://patchwork.free
Public bug reported:
After upgrade to 18.04 (bionic) I've encountered the following
regression: wired network connection does not work, when system is
resumed from suspend.
Reloading the kernel driver module seems to help:
sudo modprobe -r r8169
sudo modprobe r8169
Could this be fixed structural
-
$ env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug
/var/crash/_usr_bin_gnome-shell.1000.crash
*** Send problem report to the developers?
After the problem report has been sent, please fill out the form in the
automatically opened web browser.
What would you like t
@Daniel
Even
env -u DISPLAY -u WAYLAND_DISPLAY ubuntu-bug
/var/crash/_usr_bin_gnome-shell.1000.crash
does not provide needed link.
Are there any system settings that can affect this behavior?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1741886/+attachment/5034294/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpa
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1741886/+attachment/5034293/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https:/
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1741886/+attachment/5034292/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.laun
apport information
** Tags added: apport-collected
** Description changed:
Upon physical disconnect/connect of a monitor (connected via HDMI) shell
crashes with signal 11.
$ lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
$ apt-cache policy gnome-shell
gnome-sh
Well, I have done what you suggested. Invoking ubuntu-bug on a crash
file creates corresponding upload* files but does not print any links.
--
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/
@Daniel
The above commands do bring me to a web-page, but there are no uploaded
relevant error reports, although I see them in /var/crash
** Attachment added: "/var/crash screenshot"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1741886/+attachment/5033441/+files/20180108_ls_var_
Public bug reported:
Upon physical disconnect/connect of a monitor (connected via HDMI) shell
crashes with signal 11.
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gnome-shell
gnome-shell:
Installed: 3.26.2-0ubuntu0.1
Expected is that physical discon
The worst thing one can do it so maintain his position instead of apologising
after being rude and being called out on that.
At least one workaround was proposed even in this very thread.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to g
Another possible duplicate:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687262
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1676547
Title:
No network connectivity
Alex, how much did you pay for your copy of Ubuntu?
The problem is frustrating, but:
1) these people don't owe you anything
2) this is FOSS - go and do it yourself
3) solutions do exist.
Drop that tone!
Am 29.08.2017 9:55 nachm. schrieb "Alex" :
> what the f*cking bullshit 21st century and
Public bug reported:
It's an error that appeared on booting after unproper shootdown.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: docbook-xml 4.5-7.3
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
NonfreeKernelModules: nvidia_
Public bug reported:
I play this IT music file. It has good ending, in this player i don't
hear it: i hear only cropped sound and last seconds don't play. On Win32
I played it in ModPlug and it was ok.
Ubuntu 16.04.02 LTS x64.
totem:
Installed: 3.18.1-1ubuntu4
** Affects: totem (Ubuntu)
I
It affects me as well (Ubuntu 17.04). Screenshot is attached.
** Attachment added: "Screenshot-20170624234111-1252x899.png"
https://bugs.launchpad.net/ubuntu-gnome/+bug/1687252/+attachment/4902443/+files/Screenshot-20170624234111-1252x899.png
--
You received this bug notification because you
This is the exact discription of who my trackpoint works on Ubuntu now:
I am unable to achieve acceptable results with all the different knobs
that are available. If I tune down acceleration, I am able to do
detailed pointing, but the stick is generally so slow, that it takes
ages to cross the sc
Public bug reported:
Hello. I've tried to write on askUbuntu and to the Dell Support but got no
answers.
My problem is that I can setup my trackpoint properly on Ubuntu. It works
awesome on Windows with or without drivers installed.
I've come across this thread
https://bugs.launchpad.net/ubunt
I have this bug on Ubuntu 16.04 x64 too.
Some people say switching to setxkbmap helps: https://toster.ru/q/72254
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1370953
Title:
layout swi
Unchecking "Auto power-on" in Blueman PowerManager plugin configuration
solved this issue for me.
Additionally (or alternatively) consider unchecking "Blueman Applet" in
"Startup Applications Preferences".
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
Upon resuming system from suspend I observe graphical artefacts.
This is a regression, since I've noticed this behaviour only after
latest updates.
Rebooting system resolves the issue.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSig
** Attachment added: "bug_2017-03-24_22-22-32.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1675934/+attachment/4845050/+files/bug_2017-03-24_22-22-32.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
http
For me, the bug permanently disappeared a few months ago. Ubuntu 16.04.
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1622955
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
This bug is still affected me in Debian Sid (currently 9.0).
I affected with i3lock.
Sometimes, if wait about 3-4minutes, i3lock allow me to reenter
passphrase, but sometimes I have to reboot my laptop...
--
You received this bug notification because you are a member of Desktop
Packages, which i
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1652253/+attachment/4808955/+files/ProcEnviron.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/b
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1652253/+attachment/4808954/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.n
apport information
** Tags added: apport-collected
** Description changed:
[ 3122.921] (EE)
[ 3122.921] (EE) Backtrace:
[ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
[ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69)
[0x559ad2d8ad69]
After some update or some package installation the problem is fixed now.
Simultaneously, a similar problem with Skype video is fixed too.
I do not know what exactly fixed the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserv
Public bug reported:
[ 3122.921] (EE)
[ 3122.921] (EE) Backtrace:
[ 3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
[ 3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69)
[0x559ad2d8ad69]
[ 3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f500
Public bug reported:
This is important gameplay feature, and seems that this was changed by
somebody newer played mines, wasn't it so?
** Affects: gnome-mines (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packa
Why is this marked Expired?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1622955
Title:
VLC automatic video output malfunctions on Intel HD Graphics 520
(Skylake)
The same issue.
Dell latitude E6440, ubuntu-gnome 16.04
$ lspci -nn | grep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller [8086:0416] (rev 06)
$ uname -a
Linux pcname 4.4.0-45-generic #66-Ubuntu SMP Wed Oct 19 14:12:37 UTC 2
Created a new report:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1635830
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1632123
Title:
Nautilus "Open in Terminal" is per
Public bug reported:
When i select commands from Nautilus window bar menu such as "New Tab",
"New Folder", "Open in Terminal", the system freezes a bit and the
processor usage can reach 60% on a 6th generation Intel Core i7.
For example, "Open in Terminal" opens the terminal in the current folder
1 - 100 of 228 matches
Mail list logo
