as of this morning's updates, this problem seems to have disappeared.
I've been able to log out and back in several times to my ubuntu wayland
session, at least on my i915 machine (the dell laptop).
nb: this morning's updates updated gnome-session-bin and ubuntu-session
to 3.33.92-1ubuntu1, gdm3 t
My point regarding gnome-session-wayland.target is that if we're seeing
different filenames for that file (assuming they're functionally the
same) and mine definitely comes from gnome-session-bin, does that
suggest we're running different gnome-session-bin versions? And seeing
as you're not reprodu
minor contextual note: It took me a little while to get the other
machine, ssh in (offending ssh key to resolve), call up this page to
remind me of the exact commands. The point of which is to say, these
weren't taken *immediately* after the logout, but at least a minute
later, certainly beyond tha
journalctl -b output as attached
loginctl as below:
rachel in ~ at rainbow
ā loginctl
SESSION UID USER SEAT TTY
1 1000 rachel seat0 tty2
3 1000 rachel pts/0
2 sessions listed.
rachel in ~ at rainbow
ā loginctl show-session 1
Id=1
User=1000
Name=rachel
Timestamp=Tue 2019-09
It is definitely /usr/lib/systemd/user-gnome-session-wayland.target.
dpkg -S on that file gives gnome-session-bin which is on version
3.33.90-2ubuntu2. dpkg -S on the .service file gives no match.
This problem didn't start on upgrade to the 5.2 kernels, which happened
a few weeks(?) earlier, but i
With --systemd removed as directed I still ended up stuck on a black
screen, except this time it had a flashing white text cursor in the top
left.
(BTW reboots occurred between each test, somewhat perforce...)
--
You received this bug notification because you are a member of Desktop
Packages, wh
I tried (just now) deliberately leaving it longer than 30 seconds to
come back after a logout. In fact left it longer than 60 seconds.
Nothing happening. I wasn't logged in via ssh as well at the time (I
hadn't thought the systemd --user instance was related to the ssh
session before so presumably
the i915 one (Dell XPS 13 9370) is the one with automatic login enabled.
--
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/1841915
Title:
black screen, unresponsive, after logout fro
... and the other affected machine (just checked it's still affected
today after latest updates)
** Attachment added: "lspcik-dell.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286167/+files/lspcik-dell.txt
--
You received this bug notification because you are
As attached.
** Attachment added: "lspcik.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1841915/+attachment/5286165/+files/lspcik.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
Only affects Wayland sessions, not x11. I should have mentioned it
earlier, it's been my default for some time now (because #1827428 which
still affects latest 19.10) and I forgot.
It also seems not to be the upstream bug, unless the discussion there is
going off in the wrong directions. They now
Public bug reported:
on logout the screen is black, the system is unresponsive and has to be
restarted. (Untested by me yet, but I expect ssh-ing in and restarting
gdm would work.)
I believe this may be already reported upstream here:
https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why
A bit more detail to reproduce this that I think was missed out before:
It happens when the configured desktop mode/scaling is set to a
fractional value. You can have that experimental xrandr setting set, but
be configured to scaling of 100% or 200% (but see below on latter) and
you won't see this
My bug got marked a duplicate of this one but with the latest change
that might be wrong: It affected me on a machine with AMD graphics, not
nVidia. BTW I recently tried it again on the offchance it had been fixed
since (by re-enabling the xrandr scaling setting), and it had not. Also
not fixed on
ditto upgrading in two steps bionic->cosmic->disco
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1827099
Title:
package shared-mime-info 1.10-1 failed to install/upgrade: tr
It does appear to be related to the xrandr scaling experimental feature,
after all. Revert that to default and the issue disappears. Guessing
that probably makes it a mutter bug, and being of an experimental
feature at that is hopefully of interest to someone but not urgent. In
view of that didn't
Public bug reported:
This seems to have become repeatable, and applies even on the first
login session immediately after booting the computer. I don't know if
this is the right package to report against; another possible culprit:
gdm:
When I log into the default "Ubuntu" session (ie: on xorg), gd
i didn't freshly install to see it but i did create a new user, to be
sure I had utterly default settings and yes, it's there right from the
get-go with certain apps including terminal. but only in x11 (which of
course *is* still the default in ubuntu). I switched to wayland and this
problem went a
trying to get that screenshot was how i discovered it *does* appear to
be retaining stuff for a while at least. :-) I'll try to do so next time
I'm there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://
actually i think cookies are being held for at least a while, as,
sitting in the cafe, I can log out and in, and even reboot, and get
logged directly back into the hotspot. But when I come back the next day
I'm asked if I even want to accept cookies. It's that being asked to
accept cookies every da
i mean literally http web cookies from the portal page. if you ignore
the network login app (as was the case before it worked reliably), it
shows up in your normal browser. This does remember cookies, so you
don't get asked if you want to accept cookies every time you go there.
What the portal doe
Public bug reported:
This is with respect to the gnome-shell-portal-helper, part of the
gnome-shell package, which opens its own browser window to prompt for a
wifi hotspot login. It all works fine except one little papercut:
Could it remember cookies? So when I go back to the same hotspot most
d
Bug only affects X11 sessions.
I had a random urge to try out Wayland again. This issue does not arise
in Wayland. Apps that were affected under X11 are taking input focus
quite happily when launched from shell in Wayland.
--
You received this bug notification because you are a member of Desktop
it's not generally slow enough for the latter to be an issue. :-) Even
if I just go nice and slow. Click... window opens... it doesn't have
focus... It continues to not have focus until I do something that would
give it focus in the normal fashion, like clicking on it, clicking on
its dock icon
confirmed, gedit seems to be immune for some reason. pretty much
anything else i tried is not; calculator, terminal, libreoffice,
nautilus...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.ne
sublime text, slack also immune, firefox, thunderbird are not... so ok
it's not universal but *lots* of apps are affected, and the pattern
doesn't seem to be gnome/not-gnome.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
FYI problem remains with all those extensions removed.
BTW one does tend to notice it most with apps you type into. I first
noticed with terminal, where I'm used to click, then start typing, and
it's suddenly become click, click-again, then start typing. With an app
you'd tend first to click into
NB: If you launch an app from a terminal, eg: gnome-calculator, it
*does* then get the input focus; just not when launched from gnome-
shell. That's why I didn't think it was a mutter bug.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to g
Public bug reported:
Observed on upgrading to disco-proposed today...
When launching an app from the dock or from the applications grid (so i
believe it's a gnome-shell thing rather than a dock thing), the app
opens, but does not get the input focus. You have to either click in the
window, or cli
Follow up comment on the upstream bug pointed to a commit where it
suggests the rp_filter default should actually now be 2 rather than 1:
https://github.com/systemd/systemd/commit/230450d4e4f1f5fc9fa4295ed9185eea5b6ea16e
Think at this point I need to just let you guys talk amongst yourself.
:-) Fo
Reporting back on this:
The opinion there seems to be that the problem is down to the sys
net.ipv4.conf.*.rp_filter values being set to 1 instead of defaulting to
0. This is done in the procps package, and I'm guessing is the way it is
as a protection against IP spoofing. kernel doc page I was poi
Public bug reported:
As per subject. This package defines the file
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf, which
defines the uri for the connectivity check to be http://connectivity-
check.ubuntu.com
This hostname does not resolve to an IPv6 address. Therefore, even if
the use
As it recurred again today and showed no signs of correcting itself like
it did on Friday, I went ahead and reported it upstream, here:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/116
--
You received this bug notification because you are a member of Desktop
Packages, which
Noted. I see there's no report of anything similar already, and if it
was the sort of problem it looked like to me, people would be screaming
blue murder about it, so I think I'll wait and see if it recurs or
becomes an ongoing problem, rather than a one-off. Maybe my LAN was
having a bad hair
Public bug reported:
Actually this might be a heisenbug. I've had an issue with this all
morning since network-manager got an update this morning, but just now
*while this bug was being submitted* it decided to correct itself.
What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and
True. And I can confirm it's not listed in my plugins at all. (There's
just Cisco OpenH264 and Widevine). Only potentially-relevant extension
is Disable HTML5 Autoplay, which if anything should *stop* any video
being played before it gets to the software that does it.
Only other thing that seem
I agree it's a bit of a nightmare. It was the start of the day and I
literally just had Firefox-Next open, and Slack (using the app, not via
Firefox). No video had been posted to slack. I can only think some
random embedded video went by on the timeline or activities column in
tweetdeck (the on
Sure, just thought I'd better say something as it was my report
originally. :-)
--
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/1723615
Title:
gnome-shell crashed with SIGSEGV in meta_m
FWIW I can't reproduce this any more either; since 18.04 in fact I've
had no problems with gnome-shell crashing. The monitor very nearly
always does wake up when it's supposed to now (some difference in the
dpms signal being sent? Previously it would always wake for windows and
just had a hard time
Public bug reported:
The Software app launched by itself this morning to offer me a system
firmware (uefi bios) update of my Dell 9370. Presumably in its role as a
front-end to fwupd. That's not the bug, that's brilliant, that's pretty
much my last remaining reason to keep a Windows partition deal
pt upgrade
> $ sudo apt install kubuntu-desktop
>
>
> --
> Daniel Wilches
>
>
> On Thu, Mar 15, 2018 at 4:21 AM, Rachel Greenham <1724...@bugs.launchpad.net
>> wrote:
>> Well, my bug #1756036 just got (automatically-i-think) marked as a
>> duplicate o
Well, my bug #1756036 just got (automatically-i-think) marked as a
duplicate of this one, and I'm on 18.04 (gnome-shell 3.27.92-0ubuntu1)
So that's one, Daniel. ;-) I'd been getting this on some mornings, but
the bug report was getting rejected because of outdated packages until
this morning. Inter
*** This bug is a duplicate of bug 1724439 ***
https://bugs.launchpad.net/bugs/1724439
Daniel's latest comment on that bug shows that it looks like it doesn't
affect 3.27. This is 3.27. It's a shame those attachments got deleted...
--
You received this bug notification because you are a memb
It failed to hold true on day 2 anyway, as today the session didn't
survive the overnight sleep. But in any case I re-checked the bug of
mine that was marked a duplicate of this one, and saw as it was during
one of my brief try-outs with wayland, is irrelevant to my current
gnome-session woes, as I
Interesting
For what it's worth: On seeing #44 I tried turning off notification
popups and lock screen notifications and left it overnight. On waking I
had the usual problems I often (not always) have with my monitors
persuading them to wake up (one of them is a model with a known issue
with wakin
In fact I'm already on 387.22 which, I see from a nearby post on the
same forum, has the same fix:
https://devtalk.nvidia.com/default/topic/1025794/unix-graphics-
announcements-and-news/linux-solaris-and-freebsd-driver-387-22/
It hasn't helped.
TBH I don't think it applies as (fx: me reading up m
Just poking in to say this is still happening, and not magically fixed
by Artful's release date. It happened today, but trying to ubuntu-bug
the crash file failed. (It just quit when I clicked Continue.)
One difference today: Thinking maybe my screen-sleep woes were partly
because of gnome shell b
Yes, I see what you see: the borders around the tabs are missing. Not
just on the Security prefpane, on all of them, that have tabs.
But that's all that's wrong. (Or at least all that's obviously wrong.)
So while I can corroborate you, I think it's a different error and
should have a separate bug
Attached.
I'm using the Arc theme across the desktop, but no Thunderbird theme (or
rather, the default).
** Attachment added: "Screenshot from 2017-10-19 18-44-31.png"
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1721189/+attachment/4976376/+files/Screenshot%20from%202017-10-19%
Looks fine to me in 1:52.4.0+build1-0ubuntu2. I see the tabs just as
they are in the other pref panes.
Even if not, it would be a highly localised and minor problem, not at
all like the completely broken, unusable user interface, with large
parts missing or unstable, that we had as of the original
Adding this to *this* bug, despite the "Fix Released", because it
exactly matches the original post for this bug, whereas the others I've
encountered and reported on are different:
Oct 14 20:02:45 fleetfoot gnome-shell[12750]:
meta_monitor_manager_get_logical_monitor_from_number: assertion '(uns
bug #1723615 came up with this fix in place. Whack-a-mole! :-)
--
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/1717170
Title:
gnome-shell crashes with SIGABRT: mutter:ERROR:backend
I had one crash after applying this yesterday (and rebooting): it
crashed right out to the console, not even to the login screen, and when
I tried logging in again the session failed to start. But since a second
reboot it's apparently been fine. This bug went away, and so too has my
bug #1720149 (s
It just happened, so attached the crash file that was generated. NB:
gnome-shell 3.26.1-0ubuntu2
mutter 3.26.1-1
libmutter-1-0 3.26.1-1
NB: I notice there's also a libmutter-0-0 installed, possibly a hangover
from the original zesty install. but ldd $(which gnome-shell) indicates
it's linked to l
Iām afk today but will try to get this information on Wednesday.
--
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/1720149
Title:
gnome-shell segv on wake from display or system slee
That wouldn't surprise me. I've seen other reports, on IRC, to the same
effect. Sadly, displayport is not optional here, not if I actually want
to run my monitors at full resolution.
Someone mentioned it being a "known bug" in mutter? However they didn't
link to it and I wasn't at the keyboard at
Confirmed fixed for me too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1721189
Title:
Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
Status in thunderbird package
Public bug reported:
I wanted to use GnomeWeb to run Tweetdeck as a saved web application. So
I installed epiphany-browser, navigated to tweetdeck.twitter.com, logged
in, and then attempted to save it as a web application. This all seemed
to work, as well as Tweetdeck itself running apparently hap
I got here because my apport-raised bug #1721492 apparently
automatically got marked as a duplicate of this. I'm not so sure:
This happened after a kernel upgrade to 4.13.0-14-generic. Yesterday I
was happily using this system in a wayland session using nouveau. On
reboot with this update, all I s
/var/log/history.log section as per above post
** Attachment added: "part-history.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1505409/+attachment/4962744/+files/part-history.log
--
You received this bug notification because you are a member of Desktop
Packages, which is s
Public bug reported:
With this version much of the thunderbird UI is unusable and corrupted,
with massive redraw failures. This affects Xorg and Wayland sessions on
nvidia, nouveau, intel and oss radeon. (When I finally reported it, it
was on nvidia/xorg but wanted to stress it wasn't particular t
ok, same symptoms occurred with the default theme. So after all it looks
like the shell theme has nothing to do with it.
--
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/1720149
Title
well I spoke too soon. Crash occurred with the locally 'built' arc
theme. Slightly different though in that this time it *did* hang the
system. But it started with the same segv message logged. So back to the
default+Ambiance theme to test that for longer.
Problem with trying to prove a negative.
arc-theme package uninstalled and instead arc gtk & shell themes
installed manually as directed in its github page via autogen. This
appears not to be triggering the crash. even though the autogen doesn't
know any gnome > 3.22. It may be that similarly rebuilding the
arc-theme package for a gnome
I think my modeset=1 test earlier was invalid; I don't think that change
was ever applied. It *did* get applied just now with a routine dist-
upgrade, which included an update to console-setup, which forced update-
initramfs. And then the system was unbootable except via the recovery
system. syslog
It may be the Arc shell theme, in interaction with nVidia:
I was unable to reproduce the problem on the Macbook Pro using Xorg
gnome session, and that still with the Arc shell theme. Both a short
(few minutes) and long (greater than one hour) display sleeps tested.
I was also unable to reproduce
That would appear to be very different from what we're trying to report
here:
1. It's not hanging. It's presumably exiting, forcing a logout, and it
all happens before the monitors are awake enough to show a picture.
We're not in a hung state at any point.
2. It's not only suspend, it's wake from
neither change made a difference in the end. the needs-root-rights
change (instead of, not as well as, modeset) didn't help either, after a
long sleep.
Why instead-of not as-well-as? Because the manpage for Xwrapper.config
said that its default setting of 'auto' turns needs-root-rights off is
kms
... and the answer is no. After a longer display-sleep i woke it up to
find myself back at the login prompt. Definitely that and not the lock
screen.
This may in part be related to long-term issues I have with this
monitor. Early-revision Dell P2715Q 4K monitors have known firmware-
related issues
I tried the modeset change first, as that one we'd presumably prefer to
be true anyway one day, whereas giving stuff root that isn't supposed to
have root never feels right. :-)
It worked. I left it to display sleep for a couple of minutes and on
wake I came right back to the desktop. (I don't hav
I can't reproduce this in Xorg on my non-nvidia machine (on which I
normally run Wayland because I can). It appears to be nvidia specific.
--
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/b
Public bug reported:
The observable symptom is that if I go away and let the computer go
either to display sleep or suspend, when I come back and try to wake it
up again, I find myself, after sliding up the lock screen, at the gdm
login screen. I'm logged out, and logging in gives me a fresh new
s
I just got the mutter upgrade to 3.26.0+20170925~ea214fb-1. My gnome-
shell text was too big! So I reverted my local modification to the
theme's gnome-shell.css ;-) and now the gnome-shell text is the correct
size. I presume this build includes the abovementioned patch.
As this is, I think, the co
I'm looking forward to seeing how much the upstream changes fixes all
these. Yes, I also saw some of the other transient effects noted above;
the gnome-shell text part of it was just the bit I managed to isolate
and find consistency in. :-)
I had seen the need to apply scaling twice - sometimes, a
I'd like to give a fresh description of this bug. I think I can do so
more concisely, as it affects gnome-shell. I was in two minds about
whether to report it as a new bug, but honestly feared if I did so it
would just be marked a duplicate of this one and ignored. :-)
Also to update for current v
(though probably *unrelated*, I meant)
--
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/1713323
Title:
HiDPI support partially broken after upgrade to Gnome 3.25
Status in gnome-sh
Brad's comment: No, I've not seen the act of merely *launching* the
gnome tweak tool fix or alter anything in any way. In fact, though
probably related, the latest update seems to have broken its Extensions
tab, but that's another bug.
--
You received this bug notification because you are a membe
No wait, I've bethought me, actually. Partly brought on by issues with
nvidia/wayland that weren't immediately obvious - nouveau is actually
working better for me, if noticeably a bit more sluggish.
Regarding your comment:
"I think that GNOME Shell 3.25.90 doesn't really support HiDPI for X,
just
I care slightly less than I used to because I just now persuaded ubuntu
wayland session to run on nvidia-384 proprietary drivers. :-) Something
which I presume is intended to be the default behaviour at some point,
or at least for Nouveau.
So since I reported this bug the move to gnome 3.25 has ma
... or if you meant does the gnome tweak tool *itself* appear with its
user interface elements at the correct size or too small? It shows at
the correct size, including the titlebar... but actually contrary to my
original report *all* titlebars, both the system and integrated type,
are now being sh
The only scaling setting in tweak tool is the one in the Fonts section,
which appears to be exposing org.gnome.desktop.interface text-scaling-
factor. It scales the *text*. It scales all text relative to its
original size. So if I set it to 2.0 the text that's half size will be
the correct size, bu
Hope I'm not being overly pedantic:
The upgrade that originally broke it, that I applied on Aug 27, did
*not* include gnome-shell. If it had it would have been an obvious
culprit and I would have reported the bug against that instead of gnome-
session. So at the time I originally reported this bug
Spoke slightly too soon. It's fine on the Wayland machine, but a bit
more unstable on the nvidia/xorg machine, and I seem to need to select
the scale percentage twice before it properly takes effect, and it looks
like under some circumstances it can revert to the state described in
the original pos
I can confirm that including gnome3-staging solves most of my HiDPI
issues.
Nearly everything seems to work now, according to the setting in the
control panel -> peripherals -> display tab. I don't know what that is
exposing in gsettings (if it is); nothing obvious. It's certainly *not*
org.gnome.
I was changing the settings from the commandline via gsettings eg:
gsettings set org.gnome.desktop.interface scaling-factor 2
gsettings reset org.gnome.desktop.interface scaling-factor
etc. etc.
That setting never was exposed in the user interface, to my knowledge.
Rather uselessly the text-scal
Public bug reported:
After an upgrade this morning that took in the new version of this
package, and a suite of gnome-session/gnome-settings packages, which may
also be implicated, support for scaling on HiDPI screens seems to have
partially failed. Partially.
BTW I invoked the bug reporter with
Public bug reported:
First symptom noticed: That *sometimes* after logging in, owncloud-
client would fail to connect to the server, after a delay asking instead
for a password with the message something like (sorry don't have it in
front of me) "keyring service unavailable".
Second symptom, on t
Public bug reported:
During remote do-release-upgrade -d from a wily box.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: xinit 1.3.4-3
ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
Uname: Linux 4.2.0-34-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.regis
OSX and iOS, for instance, let you set this differently for each
network, but there's just the one global setting in Ubuntu. So if you
have a laptop that is only intermittently joined to a network requiring
a proxy, you have to go to network settings every time you join that
network and set the pro
when i tried it again on a separate machine also running trusty beta, i
discovered the theming issue is completely unrelated to the flash issue.
On *that* machine, i didn't install pepper flash, but i *did* reboot,
thinking the background instance of chromium-browser launched by the
session was con
Tried installing pepperflashplugin-nonfree.
*That* then works, but now chromium's "Use GTK Theme" is broken, it's
not themed correctly. Also there's a blue a on the menu button.
** Attachment added: "chromium-mistheme.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/130794
Public bug reported:
... that's what I get, every time chromium 34 tries to run a flash,
since the update was applied this morning. This was fine with chromium
33. Flash is also still happy to run in firefox.
No SEGV to trigger apport, and I can't see an obvious way to get more
debug information.
Public bug reported:
In Trusty:
An application that has been "locked to launcher", (including those
there by default) can only be clicked on once per session to actually
launch the application. After that it's unresponsive to clicks, although
right-click actions work.
Seems to affect all apps, i
Public bug reported:
(It has same look as unity-greeter in lightdm but am given to believe
lock screen is handled by gnome-screensaver; move if i'm wrong! lightdm
seems to get it wrong a different way.)
If, having made a wide wallpaper to span multiple monitors, and having
set it as your wallpape
ok, i *can* see the improvement if i view the images at full size
switching between browser tabs (which the site's own page doesn't seem
to let you do, bizarrely; initially i'd just thought they were SD
captures). Yes, 2nd image is better; but *still* it would probably be
better reflection if not c
I've got to admit, i'm struggling to see the improvement, and I *want*
to, agreeing with the request of this bug.
But perhaps the conversion to jpeg is wiping it out? Should be using a
lossless capture there, I reckon.
--
You received this bug notification because you are a member of Desktop
Pac
don't even care any more; switched to ownCloud. :-)
--
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/1193522
Title:
nautilus crashed with SIGSEGV in gtk_action_get_name()
Status in Na
Confirmed; launcher icon has returned; well, it's a new icon, but it's
meaningful, so that's my main issue sorted. :-)
I note still no raid understanding in gnome-disk-utility - array just
shows up as a "Block Device". Not terribly important to me but I guess
that's just been a decision to take th
OK, I'll upgrade this test vm all the way to saucy and see what happens.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1222776
Title:
gnome-disk-utlity and launcher/nautil
Second screenshot attached, showing same system post-quantal upgrade,
missing all raid icons and apparent desktop functionality.
** Attachment added: "Screen Shot 2013-09-09 at 12.39.54.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1222776/+attachment/3810802/+files/Sc
1 - 100 of 142 matches
Mail list logo
