I have attached a copy of the output I get with this issue.
The first error
```console
(evince:25290): IBUS-WARNING **: 10:54:21.331: Unable to connect to ibus: Could
not connect: Permission denied
```
happens immediately when I run evince. The second error:
```console
(evince:25403): GLib-WARNIN
Public bug reported:
Crashing frequetnly
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nautilus 1:42.2-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
All of us connecting from our macbooks really really resent this
decision.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1987159
Title:
Drop VNC support from GNOME Re
Public bug reported:
Ubuntu 22.04 freezes suddenly for no apparent reason. It does not respond to
any rescue key combination (Alt + SysRq + R E I S U, Alt + F2, etc).
Only with "Alt + SysRq + B" I can do a reset.
I have updated the kernel to the next version
antonio@antoniormz:/var/crash$ uname -
Public bug reported:
```
GNU Image Manipulation Program version 2.10.30
git-describe: GIMP_2_10_30
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/11/lto-wrapper
OFFLOAD_TARGET_
Same for me on Ubuntu Mate 22.04 5.15.0-52-generic and Cinnamon 5.2.7
/etc/X11/Xsession.d/30x11-common_xresources: ligne 16: has_option : commande
introuvable
/etc/X11/Xsession.d/75dbus_dbus-launch: ligne 9: has_option : commande
introuvable
--
You received this bug notification because you are
Public bug reported:
flatpak document portal session opened no listed reason for deployment
or operation
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: flatpak (not installed)
ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22
Uname: Linux 5.11.0-40-generic x86_64
NonfreeKer
And it occurred a second time, just a few minutes after I posted the
previous message. in case it is useful, I attach the output from dmesg
created while the UI was frozen, also the Xorg.log and another copy of
the output from journalctl -b-1 > prevboot.txt
Again the freeze corresponded with a mo
As requested I am adding the output from journalctl -b-1 > prevboot.txt
Just to add some further info:
* I reinstalled my Ubuntu system yesterday back to the same version (my wifi
and bluetooth were not working and I could find no way to get them back, so
this freeze has happened with a standa
1. Look in /var/crash for crash files
There are files in /var/crash but dated June 15 2021, one from
_usr_lib_slack_slack and one from _opt_google_chrome_chrome. Nothing from 21
June (yesterday) when the issue last happened.
2. If step 1 failed then look at https://errors.ubuntu.com/user/ID
Bug also occurs on gnome software in groovy
--
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/1876879
Title:
gnome-software cannot install classic snaps if a channel is selecte
** No longer affects: nautilus (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1880305
Title:
Failed to mount Windows share: Software caused connection abort
To manage no
Have created a workaround which works:
1. created directory ~/.smb
2. copied /etc/samba/smb.conf to it
3. added 'client min protocol = NT1' to [global] section.
as suggested in bug #1879776
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
Public bug reported:
Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS.
What happens:
In Nautilus (1:3.36.2-0ubuntu1) I do the following
1. Go to Other Locations
2. Click on Windows Network
3. Double Click on WORKGROUP
4. Double Click on DYLAN (the NAS at 192.168.1.5)
5. Dou
Public bug reported:
Gimp from the repositories does not have a maximize button in single-
window mode but the snap package which is a newer and stable version has
the maximize button on the title bar.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gimp 2.10.8-2
ProcVersionSignature: Ubunt
Attached is Xorg log for the boot of 4.4.0-145
** Attachment added: "Xorg log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255955/+files/Xorg.0.log.old
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Attached is a syslog for the boot of 4.4.0-145 from start up to shut
down in the way described above.
** Attachment added: "Syslog from boot of 4.4.0-145"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145
--
You received this bug notifica
Sorry I cannot collect log files for the kernel giving the bug. If I
can collect any useful information using the kernel that does work,
please let me know
** Changed in: mutter (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubunt
Sorry I cannot collect log files for the kernel giving the bug. If I
can collect any useful information using the kernel that does work,
please let me know
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
Yo
Please not that Launchpad has automatically assigned this bug to mutter,
but mutter is not installed on the notebook in question, so I have added
linux
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ub
Public bug reported:
Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core
CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this
kernel everything is blank. Just a black screen. If I change to a
terminal using Ctrl Alt F4 it is still a black screen but I can
ca
Confirmed fixed with live ubuntu, working with gnome-shell
3.28.3-0ubuntu0.18.04.4 from bionic-proposed. Thanks guys, was a pesky
bug.
--
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/bu
If the X-axis is %time for the benchmark read/write then why does it typically
decrease over time?
Surely the X-axis is the read/write speed at different positions 0-100% across
the disk, like access time?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, wh
I mean to list shares NT1 is needed with smbtree.
the server will be listed but shares will not.
we will see what happens down the road but this is actually a good thing
because of security issues with lower protocols.
--
You received this bug notification because you are a member of Ubuntu
Des
Andreas, it looks like to me that smbtree still needs NT1 to list
shares, as people harden there servers and disable less secure protocols
it will break browsing for shares.
the only way to get the computer listing with non-NT1 that I know of at
this point is with MDNS or Zeroconf/Bonjour
--
You
Andreas Hasenack, my server is nas4free (https://www.nas4free.org/)
running Samba version 4.7.6
smbstatus shows the connection with ubuntu 18.04 as SMB3_11.
ubuntu 17.10 would use NT1 by default.
so with 18.04 I would need to got to other "locations/connect to server"
and enter smb://server to b
Sebastien Bacher, I am not sure if it is documented anywhere?
I did notice that by default nautilus connects with smb3_11 to my
server.
thats good because it uses a more secure protocol but it breaks network
browsing.
if you downgrade to NT1 like I mentioned above it will work again but
with a l
Nautilus is now using protocol SMB3_11 in Ubuntu 18.04 and that breaks
browsing shares.
you could always choose "other locations/connect to server" and bookmark
the location and use a more secure protocol.
you could also install "smbclient" and edit "/etc/samba/samba.conf" in
the [global] section
This issue also applies to version 17.10. In my case, I am using gnome
desktop and the path /etx/xdg/xdg-gnome-xorg gets prepended to
$XDG_CONFIG_DIRS on every login.
Once the $XDG_CONFIG_DIRS gets beyond a certain length, applications
such as slack-desktop fails with a segmentation violation on s
Public bug reported:
erreur d'installation lors de la mise à jour.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gnome-menus 3.13.3-11ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu8
Architecture: am
Public bug reported:
SystemD 236+ seems to add support for writing to files from unit
definitions based on https://github.com/systemd/systemd/pull/7198. This
is very helpful when migrating legacy logging integrations from
14.04/upstart which is already writing to separate files.
** Affects: syste
Re-opened, as there's some interest from OEMs in seeing NM teaming
support land in 18.04.
** Description changed:
Availability:
The package is available in universe, built on all architectures.
Rationale:
- The package is a new (Build-)Depends for network-manager, for network device
bon
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/956070
Title:
[i
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/976165
Title:
[backgro
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1064862
Title:
[blueto
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
** Changed in: gnome-software (Ubuntu)
Assignee: Tony (toekneemi) => (unassigned)
** Changed in: gnome-software (Ubuntu)
Assignee: (unassigned) => Tony (toekneemi)
--
You received
This annoying bug still present in Ubuntu 16.04 LTS, 16.10 and 17.04.
It spreads everywhere through OS, only fresh Chrome is working fine and
Windows, sure
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubunt
I'm not positive when an update was pushed out that caused this - my
machine gets updates automatically every night but I rarely reboot. I
rebooted yesterday and was immediately affected by it.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
Running 16.04 and this happens when i run remmina. i have to to a
Control-C to get back to prompt.
any suggestions?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to zenity in Ubuntu.
https://bugs.launchpad.net/bugs/1467588
Title:
G
** Tags added: regression-release
** Tags added: xenial
** Tags added: packaging
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1614806
Title:
This package breaks "ark"
Public bug reported:
So i was told here:
https://bugs.kde.org/show_bug.cgi?id=367535
this mav be a package bug in ubuntu xenial, which i confirmed. There are
links to the upstream issue, which is already fixed, and a bugfix that i
would gladly wish you backport.
Description:KDE neon User Edi
I think you may be right, Henry. I went out on a walk along a country
lane this afternoon and decided to try out uNav. I don't think that app
expects the device to have a location to hand to it when it starts. Your
press an icon in the header to determine you current location, and it
worked. As I
Updated to OTA 12. Location icon now shows, but location still doesn't
not work for things like Google Maps, Here maps and Nearby scope.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpa
Public bug reported:
Since installing OTA-11 Google maps reports 'Google maps could not
determine your precise location' and Here maps says 'Can't find your
location'.
Location detection is ON.
'Using GPS, anonymised Wi-Fi and mobile network info' is selected in
Location settings.
** Affects: l
This may be the same as bug 1588459
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1588994
Title:
Location not working since OTA-11 on BQ 4.5
To manage notifications abou
= uid=1000
euid=1000 tty=:0.0 ruser= rhost= user=tony
May 17 10:31:47 river gnome-screensaver-dialog:
pam_sss(gnome-screensaver:auth): authentication success; logname= uid=1000
euid=1000 tty=:0.0 ruser= rhost= user=tony
May 17 10:31:47 river gnome-screensaver-dialog: gkr-pam: unlocked login ke
Thanks for that tip Michael. Sad, but after updating to 16.04 the
problem persists. I can't seem to find a permanent fix.
I've also changed video cards (nvidia 960 now) so the vid card itself
apparently wasn't involved. This is an upgrade install all the way from
12.04 if I remember correctly,
ged in: qtbase-opensource-src (Ubuntu RTM)
Status: New => Fix Released
** Changed in: qtbase-opensource-src (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu RTM)
Importance: Undecided => High
** Changed in: qtbase-opensou
@Selene
Just wanted to confirm that we don't need any more investigation re:
your comment #131 ( I think that may be the largest comment # I've seen
in a LP bug ), as your latest update to bug #1524133 indicated that
you'd isolated the problem to a SIM with an expired data plan?
@Timo
We should
So the latest changes in Lorn's signals6 patch can be summarized as:
1) remove QNetworkManagerEngine::requestUpdate (), which is a public
method which can trigger a WiFi scan request to NM.
This method doesn't appear to be called internally by the bearer plugin,
so if we think extra WiFi scans ar
Just a quick update to mention that the change to the NM bearer plugin
seems to have caused a regression when qtbase is installed from the PPA
onto a desktop ( for UI development work ).
To reproduce, the overlay PPA needs to be added as a software source,
then ubuntu-system-settings installed/upg
The associated version for the dbus-cpp in silo-026 is:
4.3.0+15.04.20151126-0ubuntu1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "PropertiesChang
The fix has landed in silo-026, as part of location-services version:
2.1+15.04.20151202.1-0ubuntu1
** Changed in: location-service (Ubuntu RTM)
Status: In Progress => Fix Committed
** No longer affects: sync-monitor (Ubuntu RTM)
** No longer affects: maliit-framework (Ubuntu RTM)
** No
The latest version of the patch is now in a silo-026, included as part
of a new qtbase version 5.4.1+dfsg-2ubuntu11~vivid1.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: sync-monitor (Ubuntu RTM)
Status: New => Incomplete
--
You
@Timo
As previously mentioned, I'd like to get this change out as a hot-fix,
and then do proper evaluation of the new connectivity API based plugin
with the goal to land it as part of OTA9.
@Lorn
I'll take a look at that the line you mentioned, however we need to draw
the line at some point and
Note, I've also pushed a new version based on your latest patch to my
PPA if anyone's interested in testing before it lands in silo-026:
https://launchpad.net/~awe/+archive/ubuntu/ppa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to db
@Lorn
Thanks for the update.
I usually do all my testing on rc-proposed, as it's latest and greatest.
I wasn't aware of the "ubuntu-developer" channel. I've tested on rc-
proposed/bq-aquaris.en ( #188 ) with the full set of packages from
silo-026, and everything seemed good to me.
Thar said, I'
@Lorn
Can you add some details regarding what image channel you actually used
and device for testing? rc-proposed is probably the best base for you
to use.
The "GetAll" behavior you're describing is similar to what I was seeing
with the AccessPoint objects. The code would see a "PropertiesChang
Here's my updated patch, the only difference is that it includes a
DBusConnection disconnect() call in the destructor for
QNetworkManagerInterfaceDeviceModem(), which I'd punted on for
expediency while testing earlier this week.
If doesn't include the IPv6 related fix, as this was fixed in NM
alre
@Mike
Small stutters when transitioning from mobile to WiFi or visa versa, or
stutters when scanning. The fixes to location-services and Qt both are
applicable to the latter case only...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed t
@Lorn
Did you see this recently? If so, what device and image?
As I mentioned, the mobile connection on touch doesn't support IPv6
connections.There was a bug in NM that falsely reported that a
default IPv6 route was available, but this was fixed awhile back.
Please see bug #1444162 for deta
@Lorn
Thanks for the updated patch.
The only significant difference besides the DeviceModem destructor fix
was the change you mentioned about default routes. Is there a touch-
specific bug that this fixes? On our system, the modem connection will
never be IPv6, whereas it is possible to get a
Here's a new version of the patch with all the access-point related
signals removed.
It makes no sense for any of this logic to be present in our system, as
none of our code attempts to control the network configuration via
Bearer Mgmt. With this patch, the plugin will never receive any NM
access
** Changed in: qtbase-opensource-src (Ubuntu)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: qtbase-opensource-src (Ubuntu)
Importance: Undecided => High
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => In Progress
--
You received
I grabbed your patch and incorporated most of it into my latest patch (
I left out a few of the disconnect calls for some of the other NM
interfaces not directly involved in the match rules problem ), however
it failed to build...
While trying to just pull in the pieces and resolve the conflicts w
Note, QNetworkManagerEngine::setupConfigurations() is also suspect as it
can get called from a couple of places and has a loops over the current
devices and calls deviceAdded().
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to dbus-cpp
Some more details:
- the version of the qtbase package in touch atm is: 5.4.1+dfsg-
2ubuntu10
- I checked and didn't see significant differences in the networkmanager
bearer plugin when comparing against 5.5.1, and 5.6.
- That said, there's been quite a few changes in the QDBus code,
specifical
And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8
upstart job, I'm getting a lot more detail without having to further
modify the code.
I'm seeing "Adding rule" log statements produced by
QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so
sounds like my previous
Just a quick update on my debugging.
I've verified that the NM bearer plugin's qnetworkmanagerengine class is
receiving the 'AccessPointRemoved', is matching them correctly in it's
saved list, and is called delete on the
QNetworkManagerInterfaceAccessPoint instance. The associated destructor
is c
For me the gvm blackscreen could be fixed by installing ubuntu-gnome-
desktop and then running "sudo dpkg-reconfigure lightdm". However, this
created an endless login loop for all users. The way to fix the endless
loop problem was to select the Mate desktop environment before logging
in. Then every
This is still an issue for me on 15.04. I have to alt-f1, log in and
kill gnome-screensaver. Then I need to save everything and reboot
because every few seconds the screen will turn black after doing this.
I don't use ecryptfs, I don't have several copies of gnome-screensaver
running when this h
@Thomas
What's the client component in this case, and why wasn't it responding?
Also, does this still tie into the WiFi state per the original
description?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
h
** Changed in: network-manager (Ubuntu RTM)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Prope
Public bug reported:
Error mounting /dev/sdb1 at /media/tony/Expansion Drive: Command-line `mount -t
"ntfs" -o
"uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177"
"/dev/sdb1" "/media/tony/Expansion Drive"' exited with non-zero e
@Markcortbass
Do you have the latest OTA installed?
Which app were you using when you hit the bug?
Also, it's possible that bug #1480877 might have something to do with
this, as when WiFi is enabled, and HERE Maps is run, a new WiFi scan is
triggered every 4-5s, and the resulting spike in DBus t
Note, one other observation noticed this week. If the HERE Maps
application is running and WiFi is enabled, it triggers scans every
4-5s.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchp
: New => In Progress
** Changed in: network-manager (Ubuntu RTM)
Assignee: (unassigned) => Tony Espy (awe)
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu RTM)
Importance: Undecided => High
--
You recei
** Branch linked: lp:~phablet-team/network-manager/lp1480877-wifi-rm-
dup-scan-signals
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1480877
Title:
Access points' "Proper
** Also affects: location-service (Ubuntu)
Importance: Undecided
Status: New
** Changed in: location-service (Ubuntu)
Status: New => Incomplete
** Changed in: network-manager (Ubuntu)
Status: Incomplete => In Progress
--
You received this bug notification because you are
This remains an issue in 14.04. Its really unfortunate that Ubuntu is
not supporting this Accessibility feature for people with disabilities.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs
*** This bug is a duplicate of bug 138586 ***
https://bugs.launchpad.net/bugs/138586
http://icredg.ir/vif/gfggjjqluzxqkzigahaquxh.wapzttezhijtzqkdqpvcl
Tony
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https
Also affects me
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1241972
Title:
Drag and drop from Dash to Desktop doesn't work
To manage notifications about this bug go to:
https:
So I think this bug should be split into two different bugs.
First, the original reporter filed this on an x86 machine running
Desktop, not Touch.As urfkill is still not used on the Desktop as of
the latest utopic images, I'm splitting this into a urfkill bug for the
problems described by myse
I came across the same error when running "quickly run", after I added
import pygtk
pygtk.require('2.0')
import gtk
to my FirstWindow.py (main window)
the output:
$ quickly run
/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning:
g_boxed_type_register_static: assertion 'g_type_fro
I am typing this with my now-paired keyboard. THANK YOU Jim, it just
worked!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
https://bugs.launchpad.net/bugs/1035431
Title:
bluetooh-wizard failed to connect
I just installed Ubuntu 14.04 and I'm using Nemo 1.8.4 since Nautilus
doesn't support an extra visible pane anymore (F3). I believe Nemo is
based on Nautilus and I've got the exact problem as mentioned in this
bug report. Does anyone have an idea how to fix this?
--
You received this bug notifica
Sorry, did not read it well enough. Not the "settings" missing but date
and time was not showing in top panel. Has been fixed simply by logging
out and in again.. Thanks anyway
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-cont
How can you drop such a crucial feature? Please bring F3 extra pane
back. Switched to Nemo because of it.. Thanks folks
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1196066
Title:
Same with me. Just installed 14.04 and date and time is missing from the
panel. Please fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1277791
Title:
Date and time
*** This bug is a duplicate of bug 138586 ***
https://bugs.launchpad.net/bugs/138586
http://nubira.co.il/eghtsop/ucggepphbpzszgguqsprvutjyexmkd.xrmemjggusirdzyv
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
https://bugs.launch
Dual monitor settings are lost on every power cycle of this ASUS
motherboard system.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1289428
Title:
Dual monitor layout
*** This bug is a duplicate of bug 1171342 ***
https://bugs.launchpad.net/bugs/1171342
** This bug has been marked a duplicate of bug 1171342
mouse scroll wheel not working in gedit & System Monitor
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, whi
Me too. It affects evince too, which kills me so bad I downgraded it to
13.04 versions, in which scroll still works
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1247937
Title:
Encompass wrote: "The computer should lock automatically when idle.
Instead of solving the problem you want to get rid of the feature."
But the feature only works some of the time, and the thread here makes
it clear it isn't going to be fixed while the system uses X.
A security feature that only
I don't have a problem with manually locking the screen, especially as I
have worked in secure Defence facilities where that is standard
pracrtice.
But I do have a problem with a software interface that falsely claims to
provide a facility which in fact doesn't work correctly if at all.
To elimin
Seth, thanks for the reference to bug 49579. I can see it's a messy
issue.
I don't have a problem with manually locking the screen, especially as I
have worked in secure Defence facilities where that is standard
pracrtice.
But I do have a problem with a software interface that falsely claims to
p
Public bug reported:
The "Screensaver & Lock settings dialog" for the gnome screensaver is
misleading and is a security risk.
It allows you to specify whether or not the screen will be turned off
after a certain time, and it allows you to specify whether or not the
session will lock (and require
Tested this on Ubuntu 13.04, 13.10 beta2, Linux Mint 15 Cinnamon.
Elementary OS Luna. All the same.
Irrespective of whether a machine is running gnome-screensaver or
cinnamon-screensaver, the timed screen lock does not operate in the way
one would expect.
1. If you don't set the screen to turn of
And I'd call this a major security flaw.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1063682
Title:
Screensaver settings GUI is confusing
To manage notifications a
Any ideas?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-nettool in Ubuntu.
https://bugs.launchpad.net/bugs/1174062
Title:
Ralink 3290 & UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+
1 - 100 of 460 matches
Mail list logo