I've also observed that the system crashes now when it never used to do
so. I've had to disable the monitor from the configuration unless I need
a third monitor. Got any more ideas?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter i
None of the on-screen menus for the monitors are auto. There is no auto
setting in fact.
• monitor 1 is set to DP (lower left),
• monitor 2 is set to DP (lower right),
• monitor 3 is set to HDMI1.4 (center top)
It will only dpms off if I turn off monitor 3 (HDMI1.4). My mobo has 3
monitor connect
In the past I've tried to disable audio as Google was suggesting that
was one of the issues. No joy. My computer only has the ports it has. I
believe it was 2xHDMI 1xDP. I'm using the MOBO video (no special card).
I'm not sure what the first item "Configure the monitor (in its own
menus) to not aut
Public bug reported:
DPMS off worked fine when I only had two monitors. I recently added a
third monitor to my setup. When locking the screen or timing out, the
monitor turns off as expected via DPMS, but then it wakes up within
seconds. They go back and forth blinking on and off for a while and t
Public bug reported:
Note: I don't know if this is a nautilus issue or a dock issue, but it
only affects nautilus.
When using nautilus, after some time the dock 'dots' that show the
active instances seems to double up and my single window shows two dots.
This happens most times I use nautilus.
I've noticed on Ubuntu 24.04 this appears to occur due to a mismatch
between how Xorg blanks the screen and the configuration gnome-settings-
daemon applies.
If you go into GSD -> Power -> Screen Blank and set it to "Never", then
go to Privacy & Security -> Blank Screen Delay -> Never, xset q stil
Public bug reported:
When I use the new (24.04) settings and 'Online Accounts' to connect to
Microsoft 365, it authenticates, works well for about 5 minutes and then
disconnects.
I have to remove that account and redo it every time I want to use it.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Here is the output:
$ journalctl -f
May 19 21:05:13 nitro gnome-control-c[5879]: Error showing account: Child
process exited with code 1
May 19 21:06:07 nitro org.gnome.Settings.desktop[5921]: GLib-GIO: Using
cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus
< 2.73.
n; status=Incomplete; importance=Undecided; assignee=None;
> Launchpad-Bug-Tags: amd64 apport-bug lunar
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: juglugs1974 seb128
> Launchpa
Public bug reported:
At installation of Ubuntu 23.04, and subsequently, when trying to use
Gnome Control Center to connect my Google account in Online Accounts, I
am able to enter my email address, but then the screen freezes in the
transition to the screen where I'd enter my password.
This happe
I can confirm that this issue is now resolved
On Thu, 16 Mar 2023 at 12:15, Mark Smith <2011...@bugs.launchpad.net>
wrote:
> Awesome! Thank you for your help on this.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
Awesome! Thank you for your help on this.
--
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/2011313
Title:
gnome-control-center crashes after launch
Status in gnome-control
Ahaha so ubuntu-settings was rolled out into Lunar overnight NOT
gnome-control-settings.
I had forgotten that I had originally tagged the wrong app - in fact, I'm not
going to have to go and look up the difference between them :)
So - false alarm - It's not ready yet :)
--
You received this bu
ubscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=gnome-control-center;
> component=main; status=In Progress; importance=High; assignee=
> jeremy.bi...@canonical.com;
> Launchpad-Bug-Tags: amd64 apport-bug lunar
> Launchpad-Bu
That command:
gsettings reset org.gnome.ControlCenter last-panel
Doesn't work for me - I get:
No such schema “org.gnome.ControlCenter”
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchp
And thanks for the tip ref running it without going to "Users" :)
--
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/2011313
Title:
gnome-control-center crashes after launch
As a data point, when I run gnome-control-center from the terminal I get
a "Segmentation Error" and core dump.
--
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/2011313
Title:
Public bug reported:
I had successfully opened settings and used it to change some of the desktop
options (size of the docker icons, etc.).
Then I clicked on "Users" and ubuntu-settings crashed.
Since then, I am unable to open ubuntu-settings - it will open and flash up on
the screen before cras
Not sure this was actually a bug. I reinstalled my system anyway so the
issue went away. Now marked as invalid
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubu
Changed from ding to nautilus after reading about nautilus gvfsd-trash
bug
** Package changed: ding (Ubuntu) => nautilus (Ubuntu)
** Summary changed:
- DING causes gvfsd 'Too many files open' error and fills syslog
+ nautilus causes gvfsd-trash 'Too many files open' error and fills syslog
** De
Public bug reported:
After following the instructions at:
http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results
on the 20220523 daily build of Kinetic, I used the command
zsysctl show
and was met with the message:
~$ zsysctl show
Command 'zsysctl' not found, b
No, It was a straight install with me present at the desktop computer
all the way through - no switching or even screen locking.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1967883
T
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577339/+files/Screenshot%20from%202022-04-05%2014-48-11.png
--
You received this bug notification because you are a member of Desktop
Packages, which
** Attachment added: "Screenshot from 2022-04-05 14-48-11.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1967883/+attachment/5577338/+files/Screenshot%20from%202022-04-05%2014-48-11.png
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
>From a clean install of Ubuntu 22.04 beta, I have installed VLC and Firefox
>(nightly) from Ubuntu Software (as snaps).
Neither of the two icons/graphics show up in the show applications window -
either in the thumbnails of the groups I have created, or the expanded windows
Unable to reproduce in VB environment
--
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/1952515
Title:
QA Test Ubuntu 22.04 Gnome-shell Crashed
Status in gnome-shell package in Ubun
Same issue on 21.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1881712
Title:
gnome-software says connection is metered while is not
Status in gnome-software package in Ub
Adding some cross-linking to help people who encounter this in the
future, and perhaps also help the devs:
This is discussed in the Ask Ubuntu post:
https://askubuntu.com/questions/1128164/no-suitable-destination-host-
found-by-cups-browsed
The solution there (which worked for me) is to `apt remo
ID = #3026
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3026
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3026
--
You received this bug notification because you are a member of Desktop
Packages, which is subs
Sorry, I should add that the pop-up window remained on top of all the others,
so it wasn't hidden behind anything else before I went to bed.
And although it was at the top, when I entered my password and the field went
grey, the window remained visible, but if I clicked anywhere in the window, I
Not at that time - I had just gone to bed. I had changed them earlier that day,
and the error triggered. So I rebooted. This time the error came about without
me touching it.
Journal output attached.
The bug doesn't appear to be triggered by any steps in Software-Updater
** Attachment added: "j
Two network & volume indicators also on XFCE panel.
No change even after resetting the panel (xfce4-panel -r).
I guess two is better than none. ;-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://
I *might* have a possible clue for the gdebi gui crash in Bionic.
If I right click on a .deb file and tell it to install with gdebi the gui will
crash.
If I open a terminal in the same directory as the file and launch gdebi-gtk
*.deb the gui will install and uninstall the .deb file without crash
This turned out to be a problem with the user not being in the audio and
pulse-access groups. Also the back panel speaker out only has one
channel working, however the front panel headphone connector works fine.
So I just use the front panel headphone jack.
** Attachment removed: "AlsaInfo.txt"
** Attachment removed: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837338/+files/CurrentDmesg.txt
** Attachment removed: "JournalErrors.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837340/+files/Jo
** Attachment removed: "PulseList.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1672562/+attachment/4837341/+files/PulseList.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launc
Public bug reported:
I have no audio output with the following configuration:
*-multimedia
description: Audio device
product: MCP61 High Definition Audio
vendor: NVIDIA Corporation
physical id: 5
bus info: pci@:00:05.0
version: a2
It looks like sudo 1.8.12 made it into 15.10 finally. Excellent. Apple
went the other route and locked the clock back down.
(https://support.apple.com/en-us/HT205031)
The CVE associated with this bug seems to be about the TZ (seen on
RedHat's security site:
https://access.redhat.com/security/cve/C
> You can set the time with:
> timedatectl set-time "2000-01-01 10:00:00"
Wow. Yeah, that'll make exploiting this *much* easier on desktop.
Fortunately Ubuntu Server doesn't allow this without authenticating.
--
You received this bug notification because you are a member of Desktop
Packages, w
Oh, nevermind! You're talking about outside of the sudo instance. In the
case of Cron, etc: just let *the user* decide whether they want to be
asked after the first time. Make it an option to unlock the clock,
disabled by default but still available.
--
You received this bug notification because
Kay, the update to sudo (1.8.10) actually solves this by using the
monotonic clock. All that needs to happen is for Ubuntu to udpate to it.
:)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-desktop-privileges in Ubuntu.
https:/
Indeed. Trojaning those requires waiting for the user. Why lay a trap
and wait when you can just break down the door? If I can use dogtail or
similar to automate the clock and suddenly we're in drive-by territory.
--
You received this bug notification because you are a member of Desktop
Packages,
Yup, I think so. while true; do setsid ; done; or
the like. In my tests rolling through then all took about 5 minutes, and
that was in a crappy VM with 1 core and 30% CPU being used by compiz. I
haven't gotten it to pop an escalated shell yet, but I'll poke at it
more tonight after work.
--
You r
> Without rebooting, the tty, inode, sid should change for every
terminal you open.
When I tried this on 15.04, the tty and inode didnt: only the SID
changed. Closing a gnome-terminal and reopening it got the same tty and
SID. For *additional* terminals, they got new ttys and inodes, but if
you cl
To clarify: I reboot, log in, open gnome-terminal. The tty is always
/dev/pts/0, and ls -i /dev/pts/0 shows an inode of 3. This occurs even
if I shut down and power back on, though admittedly in a VM.
--
You received this bug notification because you are a member of Desktop
Packages, which is su
Notice that only the SID changed though. That gives me a 1 in 32k
chance, and I can generate them basically at will with setsid. In my
testing so far, the inode of the TTY file for /dev/pts/0 has stayed "3"
across several reboots. If it doesn't change, then it is moot from a
security standpoint.
Tyler,
it's great that this bug will be fixed. However, I have some concerns about the
mitigations factors.
1) Timestamp: Easily found in the auth.log, and easily bypassed due to
an unlocked clock.
2) TTY: The tty of the first gnome-terminal running is (as far as I can
tell) /dev/pts/0. That's p
> Debian hasn't fixed this in squeeze or wheezy yet, it's fixed in
jessie because they have a recent enough version of sudo.
They haven't fixed it because they were never vulnerable: they don't
allow you to change the clock without a password.
> We do plan on backporting monolithic timer support,
Really? If the terminal I last ran sudo in is open still on the machine,
and it's unlocked, I couldn't simply change the time back to the
previous sudo command an escalate?
Even if it's a remote chance, it's still an easy exploit.
/var/log/auth.log is certainly readable by a program that uses a
d
Congratulations, Ubuntu team. You have now fallen behind *Debian's
Stable Release* in a security update to sudo, despite several releases
in between. They even released their newest (24 month development cycle)
in the same month as you. This has been fixed, *fully fixed*, for over a
year now. Epic
Same here with two different network printers on Linux Mint 17 Qiana XFCE
desktop.
The xfce4-panel -r command in a terminal window removes it OK though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
htt
There is now a full release of sudo 1.8.10, which works around the
security flaw introduced by policykit-desktop-privileges (Ubuntu). I
strongly suggest packaging and releasing this update ASAP.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribe
There is now a beta version of sudo (1.8.10b1) that has the timestamp
changed to use the monotonic clock. I continue to suggest that the
setting to require no password to change the clock be opt-IN rather than
opt-out.
--
You received this bug notification because you are a member of Desktop
Pac
I am affected by the missing comma problem. I am running gcalctool
6.4.1.1 (as reported with gcalctool --version) and 6.4.1.1-0ubuntu3 (as
reported by dpkg-query -l gcalctool) on Ubuntu 12.04.3 LTS which is up
to date as of today.
When I run gcalctool from a terminal, it outputs the following at
It's a bit more complicated than that, but not much: Sudo stores the SID
in the authentication file. However, setsid is installed by default, so
you can just launch processes with new SIDs until you get a match. You
can either run setsid and sudo a bunch and hope that you match up, or
you can look
Todd C Miller is working on it from the sudo side upstream, potentially
using CLOCK_MONOTONIC.
--
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/1219337
Title:
Users can cha
Michael:
But again, this totally ignores the question: Why on earth do we need that? How
many times per day are you changing your clock that this is necessary?!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubun
** Bug watch added: Sudo Bugzilla #616
http://www.sudo.ws/bugs/show_bug.cgi?id=616
** Changed in: sudo
Importance: Undecided => Unknown
** Changed in: sudo
Status: New => Unknown
** Changed in: sudo
Remote watch: None => Sudo Bugzilla #616
--
You received this bug notification be
** Also affects: sudo
Importance: Undecided
Status: New
--
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/1219337
Title:
Users can change the clock without authent
> There's a fine balance between security and usability, and not everyone is
comfortable with the same level of security. As I've mentioned before, it is
trivial to modify the defaults to achieve the level of security that is
appropriate for your environment.
If that's the case, why are you defaul
A somewhat sensible workaround I can find at the moment is to force re-
authentication every time you type sudo. The way to do this is by
adding:
Defaults timestamp_timeout=0
to the Defaults section of your /etc/sudoers
This will work on Ubuntu, OS X, and other variants.
Details can be found in
>This allows administrative users travelling with laptops to change the
timezone without getting an authentication prompt.
Why is saving the traveling admin from typing their password a couple of
times a day worth compromising security for everyone else? No,
seriously. Why?
>Your attack vector a
** Information type changed from Public to Public Security
--
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/1219337
Title:
Users can change the clock without authenticating
This is by DESIGN?
Your design is that any user can change the time, and therefore bypass the
security of sudo?
What's the justification for not having the user enter a password to change the
time? Convenience?
Marc, with all due respect, did you even read the bug?
"If you disable the sudo pas
Are you really sure users are supposed to be able to bypass sudo like
that?
** Changed in: gnome-control-center (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https:
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1184349/+attachment/3687141/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net
Public bug reported:
xscreensaver: couldn't grab pointer (already grabbed)
Xubuntu
“xscreensaver” package
Bugs
Bug #933789
Reported by ill on 2012-02-16
Tried runnining apport-collect 933789 but it is closed.
Happens intermittently on a resume from standby on Compaq Presario
Just popped in to check on this bug. I don't have the hardware I filed
this against anymore, and I'm still happy on OS X and my Macbook Air,
but I feel a responsibility to the users still stuck with this problem.
Why are you guys marking the g-p-m bug invalid? The switch to g-s-d
doesn't invalidat
I think I have found a workaround, for those running across this.
I posted some info here, in this similar bug.
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157
The practical upshot of all this is that adding the kernel parameter
acpi_backlight="vendor"
seems to give me pr
Happy Birthday Bug 527157! Gee, has it been two years already? It
feels like just yesterday I was wondering why I couldn't get more than
5-7 brightness levels! Three Ubuntu releases later, and I've had to find
two different solutions to the same problem. Maybe it's a g-p-m bug!
Maybe it's a kerne
This bug is still a problem in Oneric.The version of Gnome Power Manager
is completely different (3.1.3). Is there a fix possible for this? The
bug is exactly the same. Two brightness levels when only one is needed.
--
You received this bug notification because you are a member of Desktop
Package
71 matches
Mail list logo
