In my case it did appear to be gTile related also. Just manually
disabling the extension on the gnome extensions panel was also
sufficient to trigger a crash (presumably triggering the same path as
when the screen lock was activated). Presumably other extensions using
libst can have the same effect
Uploaded in #1871580. Looking through gnome-shell issues, #1868440 looks
like it might also be the same thing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871580
Title:
Session killed instead of
Deleting the old _usr_bin_gnome-shell.1000.crash and collecting a fresh
one.
However, a quick bit of experimentation appears to show that this crash
only occurs with extensions enabled - after globally disabling
extensions it appears to no longer occur. I haven't bisected extensions
individually,
Lots of repetitions of:
```
ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: called for pid 7223, signal
11, core limit 0, dump mode 1
ERROR: apport (pid 7294) Wed Apr 8 12:22:32 2020: executable:
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
ERROR: apport (pid 7294) Wed Apr 8 1
Session lock invoked manually (~11:00:00), lock screen displays, click
mouse to get unlock.
Screen freezes for ~10 seconds, then blanks briefly and shows login
screen.
Looks like gnome-shell crashing at about 11:00:26 - interesting lines:
Apr 08 11:00:26 kallisti gnome-shell[23758]:
clutter_act
There appear to neither be any relevant crash files (there are a couple
which predate upgrading this system to focal), nor are there any reports
on errors.u.c for this whoopsie-id.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
Public bug reported:
Running focal (updated to 2020-04-08), ubuntu-on-wayland session.
Trigger: either lock the screen manually (top-right-corner menu -> Lock)
or wait for the auto-lock timer (Settings -> Privacy -> Screen Lock).
Expected result: after unlock, previous session resumes.
Observed
Public bug reported:
This is related to #1465050.
ubuntu-release-upgrader-core: 1:16.04.16
What I expected to happen: Attempting xenial -> yakkety upgrade, using a
previously installed system with the default partitioning scheme, would
succeed.
What happened:
With a 256MB /boot [1] partition o
This is fixed in wily and debian unstable/testing (taskwarrior 2.4.x),
and I think the updated package should at least install on vivid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471423
Title:
Public bug reported:
Release: vivid (fresh install)
Packages:
network-manager 0.9.8.8-0ubuntu34
network-manager-pptp 0.9.8.2-1ubuntu2
network-manager-pptp-gnome 0.9.8.2-1ubuntu2
After installing network-manager-pptp-gnome, it is not possible to add a
PPTP VPN from the networkmanager G
Public bug reported:
Ubuntu: trusty 14.04
The python2 and python3 packages for the networkx library should
(presumably) be co-installable, but currently contain a common set of
files that cause whichever is installed second to fail.
python-networkx: 1.8.1-0ubuntu3
python3-networkx: 1.8.1-0ubuntu
Public bug reported:
Precise 12.04.4 x86_64, kernel 3.2.0-58-generic.
lspci reports:
01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev
a1)
dpkg -l 'nvidia*' | grep '^ii' reports:
ii nvidia-304 304.116-0ubuntu0.0.1
ii nvidia-319
It appears to be the same as that upstream report, yes.
The RAID name has been set by the manufacturer in this case, and to
dual-boot without re-installing everything it was necessary to use it.
Is it correct behaviour for `dmraid` to escape the space to `\x20` in
this case though, given it is a v
Public bug reported:
(see #1262151 concerning the same issue with mdadm)
Ubuntu: saucy dmraid: 1.0.0.rc16-4.2ubuntu1
System: Acer S5-391
Contains two flash drives configured as (Intel) fakeraid. dmraid detects this
array exists, and attempts to assemble it, but the resulting block device name
Public bug reported:
System: Acer S5-391
Contains two flash drives configured as (Intel) fakeraid. mdadm correctly
detects that this array exists, and shows (apparently) correct metadata for
both the overall array and the individual disks.
However, the name of the raid array contains spaces, an
I also use vertically-stacked dual monitors, however I do not see the
odd maximisation behaviour. I suspect it is significant that the two
screens have the same width, but different heights (1280x800,
1280x1024).
However, I do see the issue with maximised windows in the secondary
screen disappeari
Public bug reported:
Binary package hint: firefox
ubuntu 10.10, i386
xorg: 7.5+6ubuntu3
nvidia driver: 260.19.06-0ubuntu1
firefox 3.6.15+build1+nobinonly-0ubuntu0.10.10.1
metacity 2.30.2-0ubuntu1
After running flash content in the browser, the last frame shown remains
in some part of the graphic
A workaround, at least for the second-generation iPod Nano, as of ubuntu
10.10 is to insert the following into /lib/udev/rules.d/90-libgpod.rules
ENV{ID_VENDOR}=="*Apple*", ENV{ID_MODEL}=="*iPod*",
ENV{ID_FS_LABEL}=="*iPod*", ENV{UDISKS_PRESENTATION_NOPOLICY}="1"
This prevents any attempted mount
I note an interesting variation of this bug which I don't think anyone
else has reported (ubuntu 10.10).
I am unable to play video at any time with totem (resulting in the
pa_stream_cork() failed messageboxes as other have described).
However, using either rhythmbox (which I would naively assume
Public bug reported:
Binary package hint: gnome-panel
Binary package hint may be wrong, possible other candidates metacity,
nvidia-current.
When using a vertically stacked monitor layout (1280x1024 on top of
1280x800), with the primary monitor set to the upper screen.
The GNOME upper and lower
Followup
I'm not sure whether this is a bug with the driver (bcmwl-kernel-source)
or networkmanager (network-manager-gnome).
Looking at the state of some things in the /sys hierarchy before and
after checking "enable wireless" in network manager. I'm not sure if
these are helpful or irrelevant, b
The same bug affects me (regression on upgrade from lucid to maverick),
with the same driver (bcmwl-kernel-source).
I note for the reporter (assuming the problem is actually identical)
that right-clicking on the wireless taskbar logo and ticking "Enable
Wireless" successfully brings the device bac
** Attachment added: "Output of lspci -vvnn"
http://launchpadlibrarian.net/21034157/lspci.out
--
Intel driver gives incorrect screen size, DPI
https://bugs.launchpad.net/bugs/262781
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Attached Xorg.0.log for booting up without -dpi 112 setting in gdm.conf.
Note at line 453 the displaysize parameter is read from xorg.conf and
DPI set accordingly, followed by at line 680 the intel driver overriding
this setting with an incorrect value.
** Attachment added: "Xorg.0.log"
http:/
Public bug reported:
System: Dell Inspiron 6000, Ubuntu 8.04
Graphics successfully autodetected and set up, using "intel" xorg driver
and i915 kernel module. However, the screen size is incorrectly set and
results in a crazy DPI.
In gdm, this results in characters in the user-chooser and passwor
25 matches
Mail list logo
