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
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
Public bug reported:
kernel upgrade appeared to go OK actually; on the *second* reboot after
that, this appeared after login.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-21.22-generic 4.15.17
Uname: Linux 4.15.0-21-gen
belately thought of trying: running sudo update-initramfs -k all -c
produced no errors for both currently installed kernels:
rachel@spitfire:~$ sudo update-initramfs -k all -c
update-initramfs: Generating /boot/initrd.img-4.15.0-21-generic
update-initramfs: Generating /boot/initrd.img-4.15.0-20-g
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
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 Ubuntu
Bugs, which i
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
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
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
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
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
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
Network connection does not die. (It appeared to first time but I think
that's just my ongoing random - and irrelevant here - avahi issues on
this machine.)
But gnome-shell is *not* running after triggering the bug, so sudo
killall on it just produces "gnome-shell: no process found". So that was
t
additionally as it does seem to involve console switching and you might
think kernel to be relevant to that, i tried again after the most recent
kernel upgrade in 19.10 (5.2.20-15-generic). no change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
there are no crash files relating to when this happens. Currently
sitting at the machine that *doesn't* have autologin enabled, where it's
just happened again, there is nothing in /var/crash relating to this.
(nextcloud client keeps crashing, and there are crash files relating to
that, the most rec
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
... 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18419
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841915
Title:
black screen, unresponsive, after logout from gnome Wayland sess
Public bug reported:
This looks like a truly ancient bug: #12072. And a slightly less ancient
one #38535. But here it is in 19.04.
Every time I log into gnome, I see a "System problem detected" dialog. I
click on the button to report the problem, and the dialog disappears.
While the dialog is up,
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
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
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
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
Public bug reported:
Just happened trying to upgrade a machine in two immediate steps
bionic->cosmic->disco.
ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: nvidia-dkms-390 390.116-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
N
ditto upgrading in two steps bionic->cosmic->disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827099
Title:
package shared-mime-info 1.10-1 failed to install/upgrade: triggers
looping, abandon
NB: Post-upgrade upgraded to nvidia-driver-418 from restricted (didn't
re-enable graphics-drivers ppa) and all so far seems well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831070
Title:
package
Hello?
Still affecting Disco.
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770915
Title:
command not found: -antigen-env-setup
To manage notifications about this bug go to:
Public bug reported:
problem occurred becauuse symlink /initrd.imgpointed to old disco
initrd, resolved by forcibly recreating it, for now...?
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: initramfs-tools 0.133ubuntu10
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linu
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817924
Titl
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
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 Ubuntu
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
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I hid my earlier posts because I reckoned they were noise, tbh. This one
less so. :-)
I have replaced the firmware files with those from the windows driver as
described above and in the linked-to askubuntu. It worked brilliantly
for a few days, no problems at all, but just now failed: Similar to w
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
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723615
Title:
gnome-shell crashed with SIGSEGV in meta_monitor_mode_get
FWIW I have *not* seen this since upgrading to Bionic. It was probably
fixed sooner, when they said it was, but at some point I gave up on
Artful because of various gnome-shell problems including this, went back
to Mac, and tried again with a fresh Bionic install, where they almost
all seem to have
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
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
Public bug reported:
There's an ongoing issue with gnome-shell crashing during or on exit
from screen lock. I am no longer able to report when this happens
because apport silently refuses to send the bug report.
If the automatic whoopsie dialog opens at all (it doesn't, often), and I
click to sen
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
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 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720149
Title:
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
Public bug reported:
Today for the first time, and coincidentally looking for a different
setting, I went to the Settings->Privacy dialogue. I was also
(coincidentally for a different reason, relating to #1720149) already
tailing /var/log/syslog to a terminal.
Immediately on opening that dialogue
... 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
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
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
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
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
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
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.
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720149
Title:
gnome-shell segv
Attaching second screenshot referred to in original post...
** Attachment added: "Screenshot from 2017-10-02 11-04-16.png"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1720760/+attachment/4960369/+files/Screenshot%20from%202017-10-02%2011-04-16.png
--
You received this bug notificat
Public bug reported:
Today I learned from omgubuntu how to reset my gnome/ubuntu desktop
settings (dconf reset -f /), and thought I'd do it, seeing as I had
upgraded from a Zesty install at an earlier stage of 17.10's pre-release
period, and further customised as time went on in the normal way of
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
/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 Ubuntu
Bugs, which is subscr
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
Public bug reported:
I hit p by accident. I'll be removing the keybinding now I found
it, in org.gnome.mutter.keybindings switch-monitor. It's too common a
keystroke I hit when working under macOS that I'm just too likely to hit
it by accident. But that's my problem.
But it wouldn't be a problem
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
Confirmed fixed for me too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721189
Title:
Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
To manage notifications about this bug go to:
htt
Seems to have gone away with recent upgrades. I can't tell exactly which
as I was attempting to use wayland under amd and even under nvidia-387
(which worked fine except for a couple of random system freezes during
closing windows). Back on nvidia/xorg because of that (although not
exhaustively tes
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
Iām afk today but will try to get this information on Wednesday.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1720149
Title:
gnome-shell segv on wake from display or system sleep
To manage notific
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
Public bug reported:
This may relate to this item in the changelog for this version of gdm3:
* Drop 95_hide_x11_sessions_with_nvidia_kdms.patch:
- No longer needed with nvidia-384
I noticed before this version that indeed, if I enabled modeset on
nvidia-387 (which actually worked), I only
Public bug reported:
Dash to dock already installed and in use in the past, configured to be
along the bottom of the screen. Trying out ubuntu dock (after turning
dash to dock off), it *also* sits along the bottom of the screen.
Changing the position setting in dash to dock's settings, even though
I was operating under the assumption that having preferences leaking
from the original to the fork wasn't intended or desireable. After I
reported the bug I noticed from the description in ubuntu tweaks that it
apparently is. :-) I'll leave it with the little observation that it
*seemed* uninte
Public bug reported:
When launched on the default gnome desktop, the tray icon does not show
anywhere. Previously (in Ubuntu 17.04) it showed up in the legacy tray
area, and with Topicons Plus installed, showed up in the top bar
accordingly. Now there's no sign of it.
The application does launch
extra non-findings:
Removing nvidia driver and using Nouveau makes no difference here. (Also
Nouveau doesn't give the option of a Wayland session either, but that's
another story, except that if it had, and it worked, I'd probably be
content.)
Reverting nvidia to nvidia-381 (as I had been using o
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
Since I reported this, the Ubuntu Appindicators extension has turned up.
If I enable that, and not TopIcons Plus, and log in using the Ubuntu
desktop session rather than the Gnome one, the QT tray icons now show
up. This appears to apply both in Xorg and Wayland. This is clearly The
Future, given t
Public bug reported:
In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
enabled, the tray icons for QT apps (in my case, both owncloud-client
from the Ubuntu repos and enpass, from their own repo) show up after
first logging in. But once the screen has been left idle long enough to
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
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
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.
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'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
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
Public bug reported:
During boot, the screen goes black and this line appears at the top, in
white for several seconds:
[ 23.685148] INFO @wl_cfg80211_attach : Registered CFG80211 phy
Timestamp may vary of course. This is between the blank purple screen
post-grub and the ubuntu splash. On this
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
Public bug reported:
Expected: Raid arrays have appropriate icons in launcher/disk utility etc. Used
to be there in Precise
Actual: Icons are missing. Raid array has generic drive icon.
Compare the first screenshot, taken before upgrading from Precise to
Quantal, and the second, taken afterwards
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1222776
Title:
gnome-disk-utlity and launcher/nautilus lost all raid awareness
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
Public bug reported:
I apologise in advance for not knowing exactly what package to report
this against. Hopefully this can be triaged by someone more
knowledgeable.
I just upgraded a system from Precise, briefly via Quantal to Raring. On
Precise, a mounted RAID array showed in the Launcher and i
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
But I'm used to having the launcher on every display now!
(ducks and runs!)
I'll try it tomorrow. :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291362
Title:
Apps locked to launcher only laun
On further googling the problem may lie with rEFInd. It looks like the
problem discussed here: http://askubuntu.com/questions/295105/refind-
breaks-standby-mode-on-macbook-air-5-2
Am currently running without rEFInd (though it does mean having to
select "Windows" to boot Linux, which isn't pretty!
In case anyone ever looks at this, I thought I'd describe how to repeat
the issue more simply, though it was implied in the above.
As default, there is a launcher icon for "Files" at the top of the
launcher, under the Ubuntu logo.
Click on it once. Nautilus launches showing the home folder.
Clos
This seems to only affect upgrades from Saucy - even if the Saucy
install itself was unmodified from default (as in the case on this
machine, installed only briefly to upgrade to Trusty with).
Clearing all likely gnome/unity config has also cleared this problem.
--
You received this bug notifica
Public bug reported:
I had shut the lid to suspend the system last night. *After that* I
plugged in the mains lead.
Today I unplugged the mains lead and *then* opened the lid, and tried to
wake it, only to find it wouldn't do so. Had to force-reboot it. On
logging into desktop, this bug report go
101 - 200 of 427 matches
Mail list logo
