** Changed in: gvfs (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gvfs (Ubuntu)
Importance: Undecided => Low
** Also affects: gvfs via
https://gitlab.gnome.org/GNOME/gvfs/-/issues/287
Importance: Unknown
Status: Unknown
--
You received this bug notification because
The bug isn't ignored but implementing a new protocol is not trivial,
also you are commenting on the wrong place, Ubuntu isn't writting that
software. Stating that volunteers or companies not doing work for you
for free is unacceptable is probably not going to bring you far
though...
On the bug st
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpad.net/bugs/1898462
Title:
[groovy] Drag and drop files from Desktop to Nautilus freez
Public bug reported:
Description is almost the same as
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807534
Ubuntu 18.04.5 LTS, all packages up to date
gnome-shell 3.28.4-0ubuntu18.04.3
Sometimes gnome-shell freezes.
I can move the mouse pointer, but the rest of the UI is completel
Same issue in Ubuntu 20.10 with Slack and Brave browser
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1766230
Title:
Strange window matching behaviour between Slack and Chrome
Is it possible to say (approximately) when the update will come to
regular Groovy release?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1897224
Title:
Graphical snaps can't run in
I'm uploading the journalctl log from the current session now, because i
just tagged a file called "Akcent - Special Girl (One Love).m4a" and it
doesn't have a thumbnail shown by Nautilus.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1905100/+attac
There's no way the solution to this is implementing a new protocol to
replace SMB, that would be absurd. The discoverability and connectivity
works when the process is terminated and restarted. Clearly this is
achievable.
--
You received this bug notification because you are a member of Ubuntu
De
Not to put too fine a point on it, but actually that is exactly what
this requires. Microsoft phased out the SMBv1 protocol, (NetBios is
dead, long live NetBios), in favour of their new protocol: Web Services
Dynamic Discovery (WSD). There has been a lot of discussion and work as
to exactly HOW WS
Um, no. Microsoft did not deprecate SMB v1 for WSD, they did it because
it has a blatant security flaw in it :
https://techcommunity.microsoft.com/t5/storage-at-microsoft/stop-using-
smb1/ba-p/425858
Furthermore, SMB v2 and v3.x has been out for years, as modern
implementations of the protocol, _n
> I can browse to my SMB shares just by killing and restarting the
gvfsd-smbd process
you should register a new bug then because that's not what that one is about,
quoting the title
'gvfs can't list shares from smb servers that disabled SMB1'
--
You received this bug notification because you ar
In the very same article you linked: https://docs.microsoft.com/en-us
/windows-server/storage/file-server/troubleshoot/smbv1-not-installed-by-
default-in-windows
With SMBv1 being removed, Network Browser (which depended on SMBv1) was
removed, all of which relied on NetBios being used for discovery
*** This bug is a duplicate of bug 1857254 ***
https://bugs.launchpad.net/bugs/1857254
OMG! Back to windows to use Gimp!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1857338
Titl
I don't use Windows for serving SMB, I was simply linking the reason for
deprecation. FreeNAS, and other non-windows systems serve SMB v2 and
higher for network shares, and WSD is not present, relevant, or desired
in those configurations. WSD is not the solution, nor replacement, and
SMB v2 and v3
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
*** This bug is a duplicate of bug 1857254 ***
https://bugs.launchpad.net/bugs/1857254
Hello there! Don't install Gimp 2.10.20. On Ubuntu Software Manager
select snap/store > latest/edge > 2.10.22 and install it
--
You received this bug notification because you are a member of Ubuntu
Desktop
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Libfprint changed enough not to make this bug valid anymore, reopen if
needed but when testing with libfprint 1.90 or older.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
That panel changed recently so please test it again with the new one.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1750467
Title:
Backport upstream security fix patch
To ma
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream bugs and as such should be redirected to
the official wiki
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
This should be supported by latest libfprint.
** Changed in: libfprint (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1835522
Title:
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1101647
Title:
ID 138a:003d Validity Sensors, Inc.
To manage
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1065493
Title:
The "08ff:168f AuthenTec, Inc. Fingerprin
** Changed in: libfprint (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/744310
Title:
[138a:0005] [138a:0008] Fingerprint Vali
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/736793
Title:
[08ff:1680] AuthenTec, Inc. Fingerprint Sens
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc. AES2810 fingerpr
So, this is an issue that depends on device.
For MOH (match-on-host) devices there's no other option than doing this,
however the images are saved in a place where only root can access, so
are safe in a non-compromised system.
For MOC (match-on-chip) this is not the case so the issue is not valid
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
*** This bug is a duplicate of bug 602071 ***
https://bugs.launchpad.net/bugs/602071
** This bug has been marked a duplicate of bug 602071
[0a5c:5801] Broadcom fingerprint reader not working
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is su
This is should not be an issue anymore as fprintd saves the prints in
/var/lib/fprintd
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: fingerprint-gui
Status: Confirmed => Invalid
** Changed in: lightdm
Status: Confirmed => Invalid
--
You
This is now invalid as libfprint changed a lot, open a new bug if
needed.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/
As per upstream decision...
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to libfprint in Ubuntu.
https://bugs.launchpad.net/bugs/1819406
Title:
Found broken a
Public bug reported:
[Impact]
* We were advised by Synaptics to upgrade the existing libfprint in the
archive to include sensor support for 0xF9, 0xFC, 0xC2 as highlighted in
the following commits:
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/31319d9c6fe03f
[Test Case]
* We ha
Public bug reported:
[ Impact ]
[13359.449610] fprintd[355436]: segfault at 0 ip 7ffb9f375385 sp
7ffddc26ba90 error 4 in libfprint-2.so.2.0.0[7ffb9f36+3e000]
See upstream bug:
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/320
[ Test case ]
Build and run the tests inc
Public bug reported:
[ Impact ]
Fingerprint devices that we know are not supported, aren't properly put
in power-state mode
[ Test case ]
- Ensure you've a non-supported device from this list:
https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported%20Devices#usb-devices
- Ensure
Public bug reported:
[Impact]
On Ubuntu 20.04, with Synaptics fingerprint reader, users can use one
fingerprint to login system, but if users add more fingerprints, they
still can only one of those to login, other fingerprints do not work.
To fix this issue, we need support fingerprint identific
My apologies for sidetracking this far trying to explain differences
between discovery and browsing but there seems to be a lot of mixing the
2 as one. The fact that you have "discovered" a server you wish to
"browse" is irrelivant for this bug (afaik you shouldn't have been able
to discover it as
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee: (u
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => High
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee: (una
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Low
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee: (unas
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee: (u
** Also affects: libfprint (Ubuntu Groovy)
Importance: Undecided
Status: New
** Changed in: libfprint (Ubuntu Groovy)
Importance: Undecided => Low
** Changed in: libfprint (Ubuntu Groovy)
Status: New => In Progress
** Changed in: libfprint (Ubuntu Groovy)
Assignee: (unas
Public bug reported:
/run/user/1000/doc is a fuse.portal mount point, but statfs() return
EPERM, hence df produces an error message. Maybe statfs() is not
implemented, but it would be good to quieten this down (df even does not
allow me to ignore it, probably because it looks at statfs to find out
Here often gnome software cannot update Gitkraken snap, it shows an
error message that Gitkraken uses classic confinement.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/187687
*** This bug is a duplicate of bug 858338 ***
https://bugs.launchpad.net/bugs/858338
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gedit (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
D
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices, resu
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices, resu
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices, resu
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices, resu
This bug was fixed in the package libfprint - 1:1.90.3+tod1-0ubuntu2
---
libfprint (1:1.90.3+tod1-0ubuntu2) hirsute; urgency=medium
* debian/gbp.conf: Include debian's GNOME team preferred settings
* debian/patches (upstream cherry-picks):
- Properly handle aes3k devices, resu
Public bug reported:
Some games (I tried Portal and Tomb Raider 2013) don't go full screen
correctly. I tracked down this to a regression on package libmutter-7-0.
Tee problem occurs with latest version, 3.38.1-2ubuntu1, but when I
downgrade the package (and also the package gir1.2-mutter-7) to
3.
** Description changed:
- Some games (I tried Portal and Tomb Raider 2013) don't go full screen
- correctly. I tracked down this to a regression on package libmutter-7-0.
- Tee problem occurs with latest version, 3.38.1-2ubuntu1, but when I
+ Some games (I tried using Portal and Tomb Raider 2013,
It appears the update is being blocked by bug 1878293. Let's see if I
can unblock it...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1897224
Title:
Graphical snaps can't run in Gn
Verified fixed on groovy in libmutter-7-0 version 3.38.1-2ubuntu1
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launc
Please remember drag and drop is not expected to work due to bug
1813441. This bug is only about gnome-shell freezing.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons
in Ubuntu.
https://bugs.launchpa
You have been subscribed to a public bug:
X11, Wayland, the Gnome Desktop does not recognize mouse clicks and
drags after several tens of minutes after launching. However, it does
recognize the movement of the mouse cursor.
[How To Reploduce]
1. login in a Gnome session.
2. launch some applicati
Please open a bug with the developers at:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues
and tell us the new issue ID.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1905084
Ti
It sounds like gnome-shell is frozen/crashed and Xorg is still running.
Please:
1. Remove any gnome-shell extensions you may have installed and log out
and in again.
2. If the problem still happens, check the Extensions app and disable
all extensions. Then log out and in again.
3. If the proble
** Changed in: gnome-session (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpa
I'm guessing external monitors are probably controlled by the Nvidia
GPU. In that case please try opening the Additional Drivers app and
installing the official Nvidia driver.
** Summary changed:
- On any external monitors, wayland session has a white block on most part of
the screen.
+ [amdgpu]
Gnome Shell comes with its own dock which is hidden by default and
appears when you click Activities or press the Windows key.
Please disable Ubuntu Dock in the Extensions app and then tell us if
this bug still occurs.
--
You received this bug notification because you are a member of Ubuntu
Desk
*** This bug is a duplicate of bug 1897659 ***
https://bugs.launchpad.net/bugs/1897659
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1897659, so it is being marked as such. Please look
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1905209
Title:
gnome-screensaver is blocked by an application t
Well, with this limited dock I can't reproduce the bug because it leaves
the fullscreen.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1905186
Title:
dock and top bar flashing
Yeah I guess I should have expected that, thanks.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of
You have been subscribed to a public bug:
I have two monitors set up, and one is vertical.
Here is a video:
https://cdn.discordapp.com/attachments/653633559206166541/781166447174352936/20201121_133143_1_1.mp4
1. Ubuntu 18.04.5 LTS
2. Not sure what package this is
3. I expected the icon to go whe
Please:
1. Attach a copy of your ~/.config/monitors.xml
2. Run this command to automatically gather more info:
apport-collect 1905637
** Tags added: groovy
** Tags added: regression-proposed
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notifica
This is a bug in nautilus-desktop. Unfortunately nautilus-desktop is no
longer shipped and no longer supported in newer versions so this is
unlikely to ever be fixed.
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
D
Other than the exact line number, this looks close to
https://github.com/micheleg/dash-to-dock/issues/1332
** Bug watch added: github.com/micheleg/dash-to-dock/issues #1332
https://github.com/micheleg/dash-to-dock/issues/1332
** Also affects: dash-to-dock via
https://github.com/micheleg/das
You have been subscribed to a public bug:
When I switch on fractional scaling, and choose 125%/150%/175%,
everything gets very large. The screen can only display part of the
whole desktop. It is even larger than the 200%-scale.
P.S.
As I remember, the fractional scaling works well in May. But aft
Please reproduce the problem again, and while it is happening run this
command in a terminal:
xrandr --verbose > xrandr2.txt
and attach the resulting text file.
** Tags added: nvidia regression-update xrandr-scaling
** Summary changed:
- fractional display scale cannot work properly
+ [nvid
I can reproduce it but only in:
* GNOME Shell 3.36.4
* KDE Plasma Shell 5.18.5
But in XFCE, LXDE, LXQT, MATE and others ++ works fine
for me.
At first, I've tried to use `sudo chvt 2` for switching form KDE on tty1 to Raw
Console on tty2. After switching to tty2 ++ works as in early
days.
It do
** Summary changed:
- No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic behaviour
when user logged in.
+ No virtual terminals (CTRL+ALT+F?) when no user logged in
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutte
Confirmed these are actually the same code:
dash-to-dock docking.js line 2036
ubuntu-dock docking.js line 2051
** Also affects: gnome-shell-extension-dashtodock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-dashtodock (Ubuntu)
Status: New => Con
86 matches
Mail list logo
