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
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 Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://
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
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:
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
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
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
... 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
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
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 Desktop
Packages, wh
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
*** 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
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:
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
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
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
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
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 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
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 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
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
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
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
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%
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
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
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
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
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
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
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
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
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
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 Desktop
Packages, which is subscribed to g
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
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
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
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 Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1723615
Title:
gnome-shell crashed with SIGSEGV in meta_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
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
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
fixed for me too
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gwibber in Ubuntu.
https://bugs.launchpad.net/bugs/1112496
Title:
python-imaging broken in raring
Status in “comix” package in Ubuntu:
Confirmed
Status in “gwibber” pa
On 5/22/12 11:37 AM, Andrei Emeltchenko wrote:
> I think what happened is that designers copied Apple concept but
> unfortunately made some modifications :-(. Please if copy, then copy
> exactly!!
>
Well, except that they did *one* thing better than apple: In a
multi-monitor setup the global menu
If these comments reveal anything it's that different people want to
work in different ways. Those of us whose other main machines are Macs
want a permanently visible global menu; those whose other machines are
Windows, or just came from earlier versions of Gnome, want menus
attached to the win
Public bug reported:
was reporting a separate bug #1010858 about double icons appearing for
mounted filesystems, and it occurred to me that it was happening for
volumes I had listed in /etc/fstab with uhelper=udisks, the mechanism i
used in previous versions to mount internal drives and see them i
** Attachment added: "gnome-disks-options.png"
https://bugs.launchpad.net/bugs/1011257/+attachment/3183733/+files/gnome-disks-options.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launc
Additional note: "making it work a different way" half-worked. Using
gnome-disk-utility to set mount options to generate the /etc/fstab line:
LABEL=Spinner /media/Spinner auto nosuid,nodev,nofail,uhelper=udisks2 0
0
did allow the drive to mount from the disk utility; but after reboot, I
still got
Public bug reported:
Context was in testing and reporting bug #1011257 (reports a functional
problem with actually using this dialogue). I noticed that when you go
into "Edit Mount Options..." on a volume, the dialogue you get has an
"Automatic Mount Options" switch at the top, which defaults to "
--
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/1011265
Title:
automatic mount options switch logic is backwards
Status in “gnome-disk-utility” package in Ubuntu:
New
Bug
Further findings.
I think the reason why x-gvfs-show doesn't work is that package util-
linux needs to be upgraded to 2.21+ to support the x-gvfs options.
In the meantime I tried changing the option in my /etc/fstab to "comment
=gvfs-show", which seems to be the way to do it for older versions of
On 15/09/2012 22:06, Aleve Sicofante wrote:
what to do when the window gets narrower than the menu...
> - Whatever has been done for 20+ years with the classic menu bar in the
> window. This is not a new problem.
i think they word-wrap onto additional lines, on windows at least.
that's going to
fwiw i'd also say that for consistency's sake leave the default as-is -
not least for the reviews, where you'd have a choice between "They
changed the way menus work *again*" and "While the default menu
behaviour remains the same as before, there are now some user-
configurable options to answer lo
[x] option to show the damn global menu all the time
i believe that was the original complaint here; recently there's been
all these other options thrown in like someone *wanted* to muddy the
issue. LIM fwiw is a cute variation on the theme of having the menu on
the window, but which is just going
oddly this happened for me while trying to take a screenshot to report a
different bug. screenshot crashed out and I ended up here... Doesn't
seem relevant unless it's because I was in the process of selecting an
area to grab and that intersected nautilus/appmenu.
--
You received this bug notific
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
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
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
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
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
I'm having this problem on raring 13.04. x86_64, core-i7.
Specifically:
This machine actually has an nvidia gpu (GT520) and is using nvidia
drivers. HOWEVER, on its actual screen, which is a real TV, I'm running
XBMC. I'm trying to run the xubuntu desktop in a vncserver completely
independently o
Getting this trying to log in on an xdmcp session from a mac running
Xephyr. Not sure if this error is related to initial attempt to log in
with default Unity desktop, or subsequent attempt to log in with
Unity2d, which is at least partially functional (various display bugs
eg: short titlebars)
--
Public bug reported:
On Oneiric beta, when opening the Connect dialog to connect to a new
server, the window that opens is empty except for the buttons at the
bottom, which makes it a bit hard to use. Screenshot attached.
This actually looks like Debian bug http://bugs.debian.org/cgi-
bin/bugrepo
** Attachment added: "blank-connect.png"
https://bugs.launchpad.net/bugs/842434/+attachment/2360059/+files/blank-connect.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/842434
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/862669
Title:
gnome-settings-daemon crashed with SIGSEGV in
register_gnome_settings_plu
Incomplete? what do you want? Ask.
> Bug Watch Updater
> 3 November 2011 17:33
> ** Changed in: gnome-settings-daemon
> Status: New => Incomplete
>
> Rachel Greenham
> 21 September 2011 10:53
> Public bug reported:
>
> In the settings window, in the "S
** Attachment added: "compose-unknown-contact.jpg"
https://bugs.launchpad.net/bugs/855404/+attachment/2584597/+files/compose-unknown-contact.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://
Confirmed; since late beta sometime I noticed it was actually working.
Some usability and reliability issues remain but outside scope of this
big, so let's close it.
Sent from my iPhone
On 19 Oct 2011, at 19:56, Sebastien Bacher wrote:
> thank you for your bug report, is that still an issue? th
Public bug reported:
This has only just happened; I presume after today's update, as it was
working yesterday.
Open Nautilus window, click on Browse Network, expect to see icons for
each of my zeroconf-advertised shares on the rest of my network - mostly
macs sharing afp and sftp.
Today, only "W
--
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/878991
Title:
zeroconf-advertised network shares are missing
Status in “nautilus” package in Ubuntu:
New
Bug description:
This has
Some additional notes to cover bases:
1: System was freshly installed after 11.10 release. This has worked
since then until now.
2: Vinagre is able to see remote desktop shares on the network (again,
mostly macs doing screen sharing), so the zeroconf on the network does
appear to be working.
3:
Frustratingly the reboot *did* clear it, so I'm now unable to reproduce it,
unless it happens again. If it does, while this bug remains open, I will do
so.
Another test I wish I'd done before the reboot was to use avahi-browse to
confirm what was actually being seen.
We're not supposed to have an
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/855404
Title:
"Lock screen after" setting in Screen is ignored
Status in “gnome-control-center” package in Ubuntu:
New
B
Public bug reported:
In the settings window, in the "Screen" preferences, there are very few
options, and even they don't seem to work. :-) One of them is the "Lock
screen after" option where you can select a delay before the screen is
locked and required a password to regain access.
I have this
The "Turn off after" option is set to 10 minutes. And the screen does
seem to turn off after that time, or as near that I've not noticed it
doing otherwise.
At some unmeasured time after that (but way, way less than an hour)
waking it again requires the password.
I see no "dim screen" option a
As attached
** Attachment added: "screenshot of screen settings"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/855404/+attachment/2436568/+files/Screenshot%20at%202011-09-21%2017%3A45%3A18.png
--
You received this bug notification because you are a member of Desktop
Pa
On 21/09/11 20:15, Sebastien Bacher wrote:
> could you stop gnome-settings-daemon, run it from a command line with
> --debug, get the issue and copy the log to the bug?
>
I may need more specific instructions on how to do that.
When i tried it using logical-to-me means, it just respawned; before
As attached. Did changed, logged out, logged in, started tailing the
.xsession-errors file for my own amusement, then left machine alone at
13:17.
Nearly forgot about it too long! but not quite. At 14:00 woke it up, and
had to enter the password.
(Copied file to new file for upload before launchi
NB: the last line in the log before the screen dimmed was:
** (deja-dup-monitor:4532): DEBUG: monitor.vala:221: Automatic backups
disabled. Not scheduling a backup.
As no timestamps on the following gnome-settings-daemon entries, and
screen was black, I don't know when they happened! :-)
--
Yo
Public bug reported:
When using Nautilus to browse network, you can see available volumes on
the various machines on the local net. Advertised afp volumes shared out
by macs or linux hosts using netatalk show up in this window, but trying
to mount them just gets you an error dialog: 'Could not dis
--
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/846473
Title:
Browse networks shows afp mounts but can't mount them
Status in “nautilus” package in Ubuntu:
New
Bug description:
W
Confirmed fixed for me now I have it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xchat-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/842434
Title:
Connect window is blank except for Close and Connect buttons
Status in “xchat-g
Was about to report this too, yes I'm seeing this, and have seen it for
the past few Ubuntu versions, but as it tended to happen when I was
distracted by going off to do something and it didn't stop me, i never
got around to posting a bug about it before.
I'm using 11.04 Natty all up to date and I
NB: As the screenshot implies, this is on i386 Natty, on a netbook; I
also, like the original reporter of this bug, encounter it on amd64
Natty machines, so architecture seems irrelevant.
And other versions back at least to Lucid (still have one of those
sitting around with a desktop).
Point of r
just hit this on first desktop login after attempted upgrade from natty
on i386 netbook. xsession-errors attached. also, some errors encountered
at end of upgrade; hadn't got as far as investigating that yet and no
idea if relevant.
** Attachment added: ".xsession-errors file"
https://bugs.lau
1 - 100 of 142 matches
Mail list logo
