I tested 95.0a1 (Nightly), and opening the hamburger menu (using the
steps I outlined above) works now.
Closing it is still partly broken though, as clicking on the menu button
doesn't close the menu; I think that is [bug
1694514](https://bugzilla.mozilla.org/show_bug.cgi?id=1694514).
For a worka
Also, I tested the 94.0a1 nightly now, and the issue is still present.
--
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/1940417
Title:
On Wayland toolbar menus are sometimes invisible/f
I ran mozregression like this (twice, to be sure):
MOZ_ENABLE_WAYLAND=1 mozregression --profile
/home/jani/.mozilla/firefox/fyaus28k.LP1940417 --bad 91 --good 89
--profile-persistence clone-first
Here's the result (it was the same for both bisects):
5:25.73 INFO: No more integr
I can't speak for Jeroen, but I played around with the upstream builds
(both 92 and 91) and my faulty profile a bit and managed to isolate the
trigger combination for this: `MOZ_ENABLE_WAYLAND=1` and setting
`layout.css.devPixelsPerPx` to my preferred value of `1.2`; either
resetting `layout.css.de
There's no gnome-shell-extension-dashtodock package for focal [1], but I
did try with Dash to Dock from extensions.gnome.org, and could not
reproduce the issue with it. I tried with the default settings, as well
as after recreating the look & feel of Ubuntu Dock as much as possible.
Dash to Dock h
Do you want another log for that? Because (as I already mentioned
above), this also reproduces when using a newly-created user, so that
means no unsupported extensions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension
I can reproduce the crash at will with the steps I listed above, so I
don't have to wait for it to happen. It also doesn't forcibly log me
out, so I can enter those commands by just having a terminal window
present when I trigger the issue. But I logged out here (after
triggering) anyway since you
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502426/+files/prevboot.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension
1. There's nothing in /var/crash
2. There are no reports on the page for this computer.
3. Done, still nothing in /var/crash.
I don't know if this means it's not a true crash, although visually all
the indications are there.
I also verified that this reproduces when using a newly-created user
(wi
** Attachment added: "syslog Stack trace"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5501476/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension
Public bug reported:
# Steps to reproduce
0. have a mouse with horizontal scrolling functionality (mine is a Microsoft
Comfort Mouse 4500 with a tilting action for horizontal scroll)
1. move mouse pointer over the dock
2. use the mouse scroller to scroll horizontally
# What I expect to happen
No
### Steps to reproduce
1. Open about:config
2. Search for autoplay in the settings
3. Set `media.autoplay.default` to `1` ("Block Audio", which is the default)
4. Set `media.autoplay.blocking_policy` to `2`
5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033
6. Try to unmute
Hi Alex!
It does not appear to have been fully fixed by Firefox 88 for me at
least, although the conditions have changed slightly, and the remaining
broken behavior is now slightly different too.
First, to update my note above: `media.autoplay.enabled.user-gestures-
needed` has been superseded by
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1874808/+attachment/5493045/+files/ProcEnviron.txt
** Attachment removed: "HookError_source_firefox.txt"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874808/+attachment/5493042/+files/Hook
apport information
** Attachment added: "HookError_source_firefox.txt"
https://bugs.launchpad.net/bugs/1874808/+attachment/5493042/+files/HookError_source_firefox.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1874808/+attachment/5493044/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bug
apport information
** Description changed:
- With `media.autoplay.enabled.user-gestures-needed` set to false and
- `media.autoplay.default` set to 1 (block audio), which is the default
- (and other autoplay-related settings in their defaults as well), a
- Twitch video can only be either paused or
I fixed this by installing chromium .deb package from Linux Mint
repositories.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1798450
Title:
[snap] File dialogs show snap's home d
** Changed in: firefox (Ubuntu)
Status: Triaged => Fix Released
--
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/1889784
Title:
Hardware-accelerated video decoding (VA-API) broke
Public bug reported:
After updating Firefox from 78 to 79, hardware-accelerated video
decoding no longer works properly in Wayland: streaming video gets cut
off with an error message from the service.
== Steps to reproduce ==
1. Follow the steps in [1] to enable VA-API.
2. Open a Youtube/Twitch v
I can confirm that 3.36.4-1ubuntu1~20.04.1 from -proposed fixed the
issue (in Boxes) for me, i.e. the dialog text is now wrapped and hence
entirely legible.
** Attachment added: "Fully visible text after installing package from
-proposed"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/
After doing manual dconf cleanup, I've been unable to reproduce the
issue. That's since posting the previous comment, so a few days now. So
I think I'll hold off on reporting this upstream for the time being, but
I'll go ahead and do that if the problem still manifests itself.
Thanks again, Daniel
I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock,
rebooted and then reproduced the issue. Luckily I've found one way to
reproduce this, albeit somewhat convoluted and still a bit unreliable,
involving Synaptic and window tiling. And as it doesn't seem to trigger
the issue when
Happened again:
May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The
compositor tried to use an object from one client in a 'wl_pointer.enter' for a
different client.
May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client
communication (pid 5170)
May 11 17:05:5
** Attachment added: "syslog.5-excerpt.log"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877568/+attachment/5369829/+files/syslog.5-excerpt.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https:
Turns out the online service was just a little slow to update, and there
are in fact reports sent. But the only one post-20.04-upgrade is [1]
from last week, which is a gnome-shell crash and IIRC, unrelated to the
terminal issue here. It seemed to be triggered by something related to
media files an
Thanks for the instructions, Daniel! I found no crash files either
locally or online, so I've implemented the workaround now, and will try
to trigger the crash again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubunt
Public bug reported:
Since upgrading to 20.04 and switching to Wayland, Gnome terminal
occasionally crashes. I interpret the corresponding logs to mean that
it's actually Wayland that fails to do something in the background,
which then takes down Gnome terminal:
touko 08 11:35:16 saegusa gnom
Public bug reported:
With `media.autoplay.enabled.user-gestures-needed` set to false and
`media.autoplay.default` set to 1 (block audio), which is the default
(and other autoplay-related settings in their defaults as well), a
Twitch video can only be either paused or playing muted; unmuting the
vi
Done. Thanks, Sebastien!
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2616
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616
Importance: Unknown
Status: Unknown
--
Public bug reported:
When trying to start a virtual machine with Gnome Boxes, I get a prompt
about keyboard shortcuts. The prompt text is localized, but translated
back to English (I think, based on [1]) it says:
Boxes wants to inhibit shortcuts
You can restore shortcuts by pressing Supe
Oh and I'm using Wayland, in case it matters here. Haven't yet tried
whether Xorg is similarly affected.
--
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/1871868
Title:
Keyboard sho
For some of the depressing history of this, see bug #875002 (which has
been incorrectly marked as fixed by someone without a clue) from way
back in 2011.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.la
Public bug reported:
I'm using 20.04 and a Wayland session. My preferred focus mode is to
have it follow the mouse cursor:
$ gsettings get org.gnome.desktop.wm.preferences focus-mode
'mouse'
Unfortunately this causes GTK apps' popup (RMB) menu to jump to the app
window corner when opened. I'm at
Happy to report that the proposed packages did fix the issue for me
also. Thanks everyone!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1798074
Title:
LIbreoffice crashes on sta
Thanks Ville making this!
--
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/1714178
Title:
Triple 4K monitor display failed (modesetting driver limited to
8192x8192)
Status in DRI:
Fix
@Marcus: yup, that seems to be it:
jani@saegusa:~$ dpkg -l 'libcpd*' 'cpdb*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Nimi
Can't speak for Stuart, but I'm the other one affected, and still so:
jani@saegusa:~$ apt-cache policy libreoffice
libreoffice:
Asennettu: 1:6.0.7-0ubuntu0.18.04.5
Ehdokas: 1:6.0.7-0ubuntu0.18.04.5
Versiotaulukko:
*** 1:6.0.7-0ubuntu0.18.04.5 500
500 http://archive.
8
Uname: Linux 4.19.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jani 1324 F pulseaudio
BuildID: 20190315094614
Channel: Unavailable
CurrentDesktop: ubunt
nSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: jani 1324 F pulseaudio
B
-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jani 1324 F pulseaudio
BuildID: 20190315094614
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 17 15:37:04 2019
Extensions: extensions.sqlite corrupt or missing
ForcedLay
If the hardware issues a hotplug irq when the cable is still connected,
there's not much the driver can do, really. We check the link on
hotplug, it's still there, do nothing. The HDMI live status checks that
have been merged *might* help a bit, but otherwise, I'm closing as
WONTFIX.
--
You recei
A new log; still nothing useful from colord AFAICT, despite the
--verbose.
** Attachment added: "Unrecoverable failure with gsd-color --verbose"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5236695/+files/joured.log
--
You received this bug notific
...except that --debug isn't one of gsd-color's recognized parameters,
and adding it caused GDM to fail to start. I changed it to --verbose
which is available.
10.08 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color
--help-all
Usage:
gsd-color [OPTI
Sure, I've now set it up thus and will post the results once I hit this
again (it seems pretty unpredictable, so could be anything from days to
weeks).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https
Here you go. Had this occur twice in a row just now, so my original
theory of the second login never failing was false.
** Attachment added: "journalctl from a boot with two dead whales"
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5231688/+files/jo
Release: Ubuntu 19.04
Package: firefox 64.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
- USER PID ACCESS COMM
efox/
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: firefox 64.0+build3-0ubuntu1
ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8
Uname: Linux 4.19.0-9-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.10-0ubuntu14
Architecture: amd64
AudioDevicesInUse:
USER
I've hit an issue, which I believe I've now isolated to have come from
upgrading fontconfig (and related packages) from 2.12.6-0ubuntu2 to
2.12.6-0ubuntu2.3 from -proposed: if I start Firefox and afterwards
start Gparted or Synaptic, Firefox starts eating up all of my CPU.
Eventually all letters in
Thanks Olivier, I've now added the link to my upstream report.
** Bug watch added: Mozilla Bugzilla #1508043
https://bugzilla.mozilla.org/show_bug.cgi?id=1508043
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1508043
Importance: Unknown
Status: Unknown
LO 1:6.0.6-0ubuntu0.18.04.1 in Bionic is likewise affected, and the
workaround also works here.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1793861
Title:
libreoffice crashes w
This happens in 18.04 too. Bug #1650076 does also, and I'm not 100 %
sure if these are two different issues or the same. I was able to
reproduce #1650076 with the steps listed there, but just before that I
had Evince following my scroll wheel despite being unfocussed, and I had
not selected anythin
** Attachment added: "pasted text is not even close to what you've selected to
copy"
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+attachment/5201768/+files/screenshot-2.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscri
Public bug reported:
== The issue ==
Search and text selection highlighting visuals get mismatched with the actual
selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2
or larger.
== Steps to reproduce ==
* Open `about:config`, find `layout.css.devPixelsPerPx` and change
All right. Thanks, Jeremy!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1747171
Title:
"New Tab" disappeared from the GNOME Terminal menu
Status in gnome-terminal package in
Okay, did it! https://gitlab.gnome.org/GNOME/gnome-terminal/issues/30
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1747171
Title:
"New Tab" disappeared from the GNOME Termina
Jeremy: If this is indeed the popular choice then I fully respect that.
I just wanted to voice my disgruntlement, since I feel the way this was
set by upstream is much simpler. Sorry for being late with it, didn't
realize this was getting overridden before the change already came into
effect.
--
I will close this now.
--
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/1140716
Title:
[regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on
Sandybridge
Status in DRI:
Won'
I will close this now.
--
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/1041790
Title:
[snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround
i915.semaphor
Urgh, I'd argue that changing this back *is* a regression. The merged
menu item has been the default since (at least) 16.04, and now the
cognitive load of opening a new tab has suddenly increased: instead of
"new terminal" I now again have to pick the one I want (which is always
tabs for me) from t
Thanks, I've now reported this at: https://gitlab.gnome.org/GNOME/gnome-
shell/issues/287
--
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/1767806
Title:
Position of left-tiled wind
** Bug watch added: GNOME Bug Tracker #749338
https://bugzilla.gnome.org/show_bug.cgi?id=749338
** Also affects: gnome-settings-daemon via
https://bugzilla.gnome.org/show_bug.cgi?id=749338
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Public bug reported:
I've had this happen a couple of times now since upgrading to 18.04:
soon (perhaps within a minute) after logging in, Gnome session ends
abruptly and I'm thrown back to the login screen. IIRC, in both
instances this occurred on the first login after boot, so it does not
reoccu
In addition to Totem, Firefox also exhibits this with fullscreen HTML5
video. Here's a good test: https://www.youtube.com/watch?v=5xkNy9gfKOg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs
My bug #1762400 got marked as a duplicate for this one, but I don't have
Dropbox installed.
--
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/1734891
Title:
nautilus crashed with SIGSEG
*** This bug is a duplicate of bug 1734891 ***
https://bugs.launchpad.net/bugs/1734891
Possible duplicates with bug #1607919
--
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/1762400
Haven't seen this since upgrading to 18.04, and can't reproduce it
following the instructions anymore either, so it appears to be fixed.
** Changed in: firefox (Ubuntu)
Status: New => Fix Released
** Summary changed:
- In Firefox 57 (Quantum), HTML links' context menu appears in the wrong
This is currently still present in Bionic's Shotwell 0.28.1-0ubuntu1.
** Also affects: shotwell via
https://bugzilla.gnome.org/show_bug.cgi?id=738486
Importance: Unknown
Status: Unknown
** Summary changed:
- issues when saving image (different from #1064332)
+ After saving image, Sh
*** This bug is a duplicate of bug 1724439 ***
https://bugs.launchpad.net/bugs/1724439
** Description changed:
Had been AFK for a couple of hours with the display turned off, came
back and turned it on when this occurred.
- I've redirected Gnome shell related log etries away from my sy
Looks like you can still enter 'Print' in dconf-editor for a custom
action (/org/gnome/settings-daemon/plugins/media-keys/custom-
keybindings/customN/binding), so at least there's that.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnom
It seems that PrintScreen is now bound to Gnome Settings Daemon, which
is used to take screenshots instead of gnome-screenshot. Keyboard
settings (in Gnome settings) still has a screenshot shortcuts section in
the keyboard shortcut settings, but those too now only trigger Gnome
Settings Daemon's sc
** Bug watch added: GNOME Bug Tracker #794195
https://bugzilla.gnome.org/show_bug.cgi?id=794195
** Also affects: shotwell via
https://bugzilla.gnome.org/show_bug.cgi?id=794195
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of De
Public bug reported:
I am running Ubuntu 16.04 LTS on a dell inspiron 15R 5521. I had this
issue of the touchpad left click not working, so I had to reinstall
ubuntu 16.04. It was working fine until today, when the left mouse click
stopped working.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Pac
Public bug reported:
After upgrading to Quantum, the right mouse button context menu for HTML
links pops up in the wrong place when the Firefox window is pushed to
either side of my screen (so that the window takes up half of the
horizontal space). The issue appears similar to what has been report
Public bug reported:
== Steps to reproduce ==
1. Download
https://upload.wikimedia.org/wikipedia/commons/thumb/e/e1/Car_crash_1.jpg/193px-Car_crash_1.jpg?download
2. Open the image in Shotwell Viewer: $ shotwell 193px-Car_crash_1.jpg
3. Select File > Save As...
4. Select OK (without changing Form
Public bug reported:
For optimizing files in-place with jpegtran, especially from scripts and
when dealing with lots of pictures, it's handy to be able to specify
input file as -outfile.
But there's a catch:
Steps to reproduce:
0. Have a large JPEG file, or, alternatively, somewhat slow CPU
1. `
** Bug watch added: GNOME Bug Tracker #409779
https://bugzilla.gnome.org/show_bug.cgi?id=409779
** Also affects: aisleriot via
https://bugzilla.gnome.org/show_bug.cgi?id=409779
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of D
** Changed in: nvidia-graphics-drivers-304 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639051
Title:
gnome3 h
304.134 was available in the repository and so far looks like it fixes
the problems I had with 304.132.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639051
Title:
** Bug watch added: Debian Bug tracker #659036
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659036
** Also affects: gnome-keyring (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659036
Importance: Unknown
Status: Unknown
--
You received this bug notification bec
alwuzomondo:
Ah, you had/have it available. I don't and had to go for 304.117.
Thanks for answering again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu.
https://bugs.launchpad.net/bugs/1639051
T
Here's mine, although I already downgraded the driver before I ran the
command.
** Attachment added: "nvidia-bug-report.log.gz"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1639051/+attachment/4772565/+files/nvidia-bug-report.log.gz
--
You received this bug noti
alwuzomondo:
Thank you for answering. Were you able to force the version back to 304.131 or
to a much older one? I'm only seeing 304.117 as available version apart from
the current.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia
Yes, can't use OpenGL interface applications like Blender 2.78a anymore
after the driver update. I can run it but it doesn't draw the geometry
correctly and then gives a black screen with a text cursor. Blender
requires opengl 2.1 which I have and it worked fine before the update,
also running Blen
Public bug reported:
can't install ubuntu 16
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Aug 29 16:00:26 2016
E
Haven't seen this once since upgrading to 16.04 back in April, so I'm
pretty sure the issue has been fixed. Yay!
** Changed in: xorg (Ubuntu)
Status: Expired => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in
Everyone hitting the issue, please attach
/sys/kernel/debug/dri/0/i915_vbt (or if that doesn't exist,
i915_opregion).
Mika, just an idea... please check the vswing/pre-emph values in VBT.
I'm not sure if we parse them in either the driver or intel_bios_reader.
Check the VBT spec. Perhaps the VBT v
(In reply to Daniel Vetter from comment #126)
> (In reply to Chris Rainey from comment #119)
> > Confirming that "intel_idle.max_cstate=1" has solved my complete freeze
> > issues on Bay Trail running Linux 4.1.13(Slackware64-current(pre-4.2)
> > formerly running Ubuntu 15.04/15.10 with stock kerne
(In reply to Christopher M. Penalver from comment #27)
> jan iversen, could you please post the direct URL of the notes of the gerrit
> you are referring to (versus make folks dumpster dive for it via a search
> engine, etc.)?
Not a bad idea, will have to dig it out.
>
> There is nothing in
> http
It turns out the fix, created other problems, please look at the notes
on the gerrit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/831305
Title:
[Upstream] Numbering mis-indents
(In reply to Sander Eikelenboom from comment #250)
> Is there a way to get off the CC-list of this slightly depressing kind of
> "catch-all" bug ?
CC list is at the top right corner. Choose the address, tick "Remove
selected CCs", and hit Save Changes.
I've done this for you now.
--
You receive
(In reply to Sander Eikelenboom from comment #250)
> Is there a way to get off the CC-list of this slightly depressing kind of
> "catch-all" bug ?
CC list is at the top right corner. Choose the address, tick "Remove
selected CCs", and hit Save Changes.
I've done this for you now.
--
You receive
(In reply to John from comment #102)
> Given Luka Karinja's results, I checked my kernel args to see if something
> else could account for my results. I found - i915.i915_enable_rc6=1
> i915.lvds_downclock=1 i915.semaphores=1 i915.i915_enable_fbc=1.
i915.i915_enable_rc6 and i915.i915_enable_fbc h
(In reply to michel.verbist from comment #7)
> And my sound works again.
>
> Thanks for everything.
Awesome, thanks, closing.
--
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/1458136
(In reply to Robert Ancell from comment #1)
> We are currently working around this issue in Ubuntu 15.04 by reverting that
> one commmit.
That one commit being
commit 7d9a74622e5a936e4860fcef8358619bf59adae8
Author: Chris Wilson
Date: Mon Jun 15 14:16:34 2015 +0100
sna: Be robust in handlin
With more testing I found that the context menu position depends
(perhaps solely) on whether my mouse pointer is on the left side or the
right side of the horizontal half of the rightmost monitor: if you
imagine a vertical line dividing the rightmost monitor's display area
into two equal-sized halv
Just adding a note that this does still occur under 14.04, to which I
recently upgraded. Naturally this was to be expected, given that the
issue first occurred after switching to the Trusty HWE pack in 12.04.
--
You received this bug notification because you are a member of Desktop
Packages, whic
Spoke too soon: looks like the context menu for links just also turned
affected. I swear they worked fine when I was writing the previous
comment!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.la
I can reproduce this on a two-monitor setup: right-clicking in Chromium
on the right monitor brings up context menu on the left monitor. Right-
clicking on the left monitor works as expected.
I cannot reproduce the workaround: here the context menu opens on the
left monitor no matter how close to
(In reply to matthias.a.lee from comment #27)
> Is there a build including that patch or will I have to build it myself?
As an upstream we don't provide builds, you're expected to be able to
apply and test patches. Sometimes your distro developers may be able to
help.
--
You received this bug no
1 - 100 of 254 matches
Mail list logo
