@Sander50: What workaround??
@pitti: In general I think it *doesn't* work fine to eject all usb
devices - especially external USB hard drives - flash drives seem to
work okay - except they can't be remounted afterwards and need to be
physically removed and reinserted first - but I have an
But it seems like this (not being able to eject devices using nautilus /
drive-mount applet) is definitely a new problem - at least for me I
never had problems like this before, and thus this a regression for me -
has anything else changed such as the method used to eject the devices
which could
Interestingly, while I can't eject my external usb harddrive, I can
still eject my usb thumb drive, so I have attached the output from
DebuggingRemovableDevices from the wiki with first the usb flash (thumb)
drive which can be correctly ejected, and then the external usb
harddrive which can't be
udev.log with thumb drive
** Attachment added: udev.log with thumb drive
http://librarian.launchpad.net/7336300/udev.log
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
dmesg with thumb drive - note before running these debugging steps I had
previously inserted and ejected the drives a couple times so only the
last bit is probably relevant
** Attachment added: dmesg with thumb drive
http://librarian.launchpad.net/7336304/dmesg.txt
--
do not eject all
devices.txt listing sd* devices in /dev
** Attachment added: devices.txt
http://librarian.launchpad.net/7336305/devices.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Attachment added: lshal with thumb drive
http://librarian.launchpad.net/7336301/lshal.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
other outputs requested - ie id etc
[EMAIL PROTECTED]:~$ id
uid=1000(alex) gid=1000(alex)
groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),110(netdev),111(lpadmin),113(powerdev),114(scanner),116(admin),1000(alex)
[EMAIL PROTECTED]:~$ id hal
id: hal: No such
Now is attached the same but when the external usb harddrive is attached
- I also tried ejecting it so the output in gvm from trying to do that
is there too
** Attachment added: gvm.log with external usb harddrive
http://librarian.launchpad.net/7336311/gvm.log
--
do not eject all
** Attachment added: lshal with external usb harddrive
http://librarian.launchpad.net/7336312/lshal.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct
dmesg output for external usb harddrive which cannot be ejected - Since
I did this after the thumbdrive stuff above it also includes that as
well...
** Attachment added: dmesg with external usb harddrive
http://librarian.launchpad.net/7336317/dmesg.txt
--
do not eject all USB/Firewire
ls of /dev/sd* with external usb harddrive connected
** Attachment added: devices.txt
http://librarian.launchpad.net/7336319/devices.txt
--
do not eject all USB/Firewire devices
https://bugs.launchpad.net/bugs/63090
You received this bug notification because you are a member of Ubuntu
The naming could definitely be better, as with multiple devices, it is
not easy to identify which one is which when you want to unmount / eject
a specific one.
--
Volumes change name when mounted/unmounted in Nautilus
https://bugs.launchpad.net/bugs/85635
You received this bug notification
I am currently on holiday, and will be back in a week, but this occurred
for me with both dapper and edgy. I have not yet tried fiesty, but will
once I get back home. What is the expected behaviour that I should be
seeing in this case? Cheers
--
inconsistent handling of external usb devices
*** This bug is a duplicate of bug 94588 ***
https://bugs.launchpad.net/bugs/94588
** This bug has been marked a duplicate of bug 94588
[apport] sabayon-apply crashed with ValueError in c2py()
--
sensor-applet starts showing wrong devices
https://bugs.launchpad.net/bugs/114804
You
This was fixed in fiesty UNTIL hal version 0.5.8.1-4ubuntu12 was
published - the problem seems to be the readdition of 10.storage-
policy.fdi - if this is removed, it works as expected - ie. I can
continously mount and unmount a device from nautilus.
So I would say the problem is actually in hal,
This is a regression due to the addition of 10-storage-policy.fdi, and
more specifically the requires_eject policy for usb devices. IMO this is
incorrect and should be removed.
--
Nautilus and hal can't umount usb hd disk
https://launchpad.net/bugs/99498
--
desktop-bugs mailing list
This 'fix' has caused a number of other problems - see: #99498
https://launchpad.net/ubuntu/+source/hal/+bug/99498
--
Desktop suggests using eject in the drive icons context menu, but it is
missing
https://launchpad.net/bugs/97366
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
This is also affecting a number of other users:
http://ubuntuforums.org/showthread.php?t=398262
http://ubuntuforums.org/showthread.php?t=398704
Can the requires_eject policy for all usb storage devices please be
changed to false, as in general unmounting is a more desirable feature -
especially
I am seeing this same bug on my MacBook Pro 5,1 with Ubuntu 8.10 using
the mactel-support ppa with all relevant packages from the PPA installed
and kernel modules loaded. This includes the updated package of gnome-
power-manager from the PPA, and the only way to fix the problem is to
disable the
By improving the driver, do you mean getting it to scale values based
upon which machine it is running on to report a larger dynamic range
under 'normal' light conditions? This should be relatively straight
forward, provided we can obtain some data about which machines report
these lower values -
I guess we need to first get the values which the light sensor reports
for each of the different models under varying light conditions - then
we can identify which models need correcting / scaling for - ie. as I
mentioned before my MBP 5,1 reports only 4 out of 255 in a reasonably
well lit room so
See new bug report which I just opened for a patch to add light_scale to
applesmc-dkms https://bugs.launchpad.net/mactel-support/+bug/315485
--
Backlight keeps getting darker on MacBookPro
https://bugs.launchpad.net/bugs/285815
You received this bug notification because you are a member of
Thanks for the feedback rydberg - after looking into it some more it
seems the new MBP / MBA's use the 10 byte light value from the left
sensor as follows:
first 2 bytes seem to always be 01
next 2 bytes are a big endian 16-bit value of the ambient light value with a
maximum value of 65535
next
Actually scrub the previous patch - this one is much simpler and doesn't
break the case for the old machines.
** Attachment added: Improved patch
http://launchpadlibrarian.net/21101822/applesmc-dkms-light-sensor-fix.patch
--
Backlight keeps getting darker on MacBookPro
3.2.0 has been released:
ftp://ftp.gnome.org/pub/gnome/sources/ekiga/3.2/
--
Update to 3.1
https://bugs.launchpad.net/bugs/341367
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to ekiga in ubuntu.
--
desktop-bugs mailing list
This also affects other mail applications like gnome-gmail (bug #729357)
and desktop-webmail since neither can set themselves as the default mail
application - at the moment there is a patch for gnome-gmail in the
attached bug, but it would seem a better solution would be to fix this
in
Public bug reported:
Binary package hint: gnome-power-manager
upower 0.9.8 supports controlling keyboard backlights and exposes an
appropriate dbus interface to control them.
g-p-m can simply access this to control keyboard backlights in much the
same way as it does for lcd / display
** Patch added: Patch to implement keyboard backlight support in g-p-m 2.32
for natty
https://bugs.launchpad.net/bugs/724324/+attachment/1868852/+files/99-keyboard-backlight-support.patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I've got packages in my ppa to test this implementation under maverick
if interested (currently waiting to build...)
https://launchpad.net/~alexmurray/+archive/ppa
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
A similar patch has been sent upstream http://mail.gnome.org/archives
/gnome-power-manager-list/2011-February/msg00017.html which should
hopefully get accepted - the upstream codebase is quite a bit different
now after transitioning to Gtk 3 and other Gnome 3 related changed so
the patch here is a
Upstream have accepted the updated patch (http://git.gnome.org/browse
/gnome-power-
manager/commit/?id=7e5fedb32bfb9dc6428c5b0eb21ef48a27602a27) so there is
no worries that we are deviating too far with this extra patch against
2.32.
--
You received this bug notification because you are a member
No worries Chris, will see what I can get together - should I file a
separate bug report for the FFE or just put all the required information
into this one?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
** Summary changed:
- g-p-m should add support for controlling keyboard backlight via upower in
natty
+ FFE: Add support to g-p-m for controlling keyboard backlight via upower in
natty
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Have updated bug description with info for the FFE. Will update again
soon once I confirm the patch is correct for Natty.
** Description changed:
Binary package hint: gnome-power-manager
- upower 0.9.8 supports controlling keyboard backlights and exposes an
- appropriate dbus interface to
Have just finished successfully building and testing the patch in Natty
(see description for link to build log). Any update on the FFE? Any more
info required?
** Description changed:
Binary package hint: gnome-power-manager
The version of upower (0.9.8) in Natty now has support for
@pitti - Any update on when this will be uploaded?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
https://bugs.launchpad.net/bugs/724324
Title:
FFE: Add support to g-p-m for controlling keyboard
Thanks Chris.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
https://bugs.launchpad.net/bugs/724324
Title:
FFE: Add support to g-p-m for controlling keyboard backlight via
upower in natty
--
@Chris - sorry to bug you but just wanted to ping you again about
sponsoring this Thanks.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
https://bugs.launchpad.net/bugs/724324
Title:
FFE: Add
*** This bug is a duplicate of bug 459639 ***
https://bugs.launchpad.net/bugs/459639
** This bug is no longer a duplicate of bug 532436
nvidia driver sometime does not load at boot
** This bug has been marked a duplicate of bug 459639
X server starts randomly in failsafe when starting
This is due to a crash in upowerd which is inturn caused by a bug in
libusb, marking as dupe against bug #427805
--
No battery level indication
https://bugs.launchpad.net/bugs/85
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 427805 ***
https://bugs.launchpad.net/bugs/427805
** This bug has been marked a duplicate of bug 427805
usb_find_devices() crashed with SIGSEGV in free()
--
No battery level indication
https://bugs.launchpad.net/bugs/85
You received this bug
This is not a bug - what has happened here is that while your machine
was locked, someone has come along and selected 'Leave a message' and
typed in 'Give me your password!' - then when you come and unlock the
screen, the message they left it displayed for you..
Try it for yourself.
--
Funny
To reproduce, lock your screen, then click the leave a message button,
and type in ' Give me your password' or whatever you want, then click
OK. Finally unlock the screen and voila!
** Changed in: gnome-screensaver (Ubuntu)
Status: Incomplete = Invalid
--
Funny Dialog Box?
@Vladimir - that doesn't sound like a bug to me - of course it will fail
to display if set to only display when charging / discharging and
battery is at 100% with AC since it *isn't* charging / discharging, it's
full. This is just the correct, expected behaviour for that setting. If
you want it to
I'm having this problem too - I am playing a video in Totem when Skype
pops up a notification saying someone has logged off / on - this pauses
my video - and the video stays paused even after the notifcation has
gone away which I dont think should happen - instead shouldn't the
pausing only happen
Just wondering if hyperair's patch will get applied to Ubuntu's banshee
before Karmic is released?
--
design problem? infinite wait for long queue
https://bugs.launchpad.net/bugs/334809
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
This seems to be a serious regression to me - bug #426765 (which seems
to be a dup on this) suggests that commit
http://cgit.freedesktop.org/xorg/xserver/commit/?id=c1d901d723c3bee523736eacc15b44a7dff484fe
needs to be applied to xorg-server to fix this - so I suggest this bug
should be marked
@Bryce: I am pretty sure the Ubuntu xorg-server is still missing one of
the fundamental upstream patches to fix this issue - as Ive said on a
number of other bug reports which report this issue still, the following
patch is still needed:
I've uploaded a patched version of xorg-server to my PPA which should
fix this if you want to test it:
https://launchpad.net/~alexmurray/+archive/ppa
--
Karmic upgrade not shutting off backlight after time
https://bugs.launchpad.net/bugs/413168
You received this bug notification because you are
Yep, I've also got the same patch applied in my PPA and can confirm this
fixes the screen blanking.
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 413168 ***
https://bugs.launchpad.net/bugs/413168
I've uploaded a patched version of xorg-server to my PPA which should
fix this if you want to test it:
https://launchpad.net/~alexmurray/+archive/ppa
--
[karmic] display doesn't go to DPMS sleep
I've uploaded a patched version of xorg-server to my PPA which should
fix this:
https://launchpad.net/~alexmurray/+archive/ppa
--
Monitors do not sleep
https://bugs.launchpad.net/bugs/436574
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I've uploaded a patched version of xorg-server to my PPA which should
fix this:
https://launchpad.net/~alexmurray/+archive/ppa
--
g-p-m does not turn off the display after specified time-out
https://bugs.launchpad.net/bugs/415589
You received this bug notification because you are a member of
This patch is about making the applesmc driver report sensible values
for the ambient light sensor - it has already been integrated into the
applesmc dkms package in the mactel ppa so if you're running that then
you've already got it and don't need to do anything with the patch
itself.
--
@Milos - the patched version of xorg-server in my PPA has been
superseded by the official Ubuntu package, so there is no need to use my
PPA (hence why it doesn't offer any upgrade because the version in the
official PPA is newer). For me this issue is fixed by the official
package in the Ubuntu
Public bug reported:
Binary package hint: rhythmbox
Crashed when trying to use ubuntuone-music-store plugin - as am in
Australia I get the world store, and I simply clicked on the first item
listed in 'World Store Top Picks' on the front page (Oasis - Definitely
Maybe) and rhythmbox crashed. I
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41695726/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/41695727/Disassembly.txt
** Attachment added: GConfNonDefault.txt
http://launchpadlibrarian.net/41695728/GConfNonDefault.txt
As can be seen from the stacktrace this looks like a crash in the flash
player, and after uninstalling adobe flash player I can no longer
reproduce this crash. Will try later with gnash or swfdec perhaps...
this is a shame as in general the adobe flash plugin is perfectly stable
in Chrome /
*** This bug is a duplicate of bug 544864 ***
https://bugs.launchpad.net/bugs/544864
Marked as dupe against #544864 as this has a stack trace from the crash
and appears symtom-wise identical
** This bug has been marked a duplicate of bug 544864
rhythmbox assert failure: rhythmbox:
accidentally assigned to ubuntu, reverting
** Also affects: rhythmbox-ubuntuone-music-store
Importance: Undecided
Status: New
** Package changed: rhythmbox (Ubuntu) = ubuntu
** Package changed: ubuntu = rhythmbox (Ubuntu)
** Changed in: rhythmbox-ubuntuone-music-store
Assignee:
Why low importance? This crash makes the music store completely useless
when adobe-flash-plugin is installed as it consistently crashes...
--
rhythmbox assert failure: rhythmbox:
/build/buildd/nspluginwrapper-1.2.2/src/npw-rpc.c:1225: do_recv_NPObject:
Assertion `npobj != ((void *)0)' failed.
As a note - this is actually an assert failure in nspluginwrapper,
rather than flashplayer itself - which is needed for the 32-bit flash
player on 64-bit ubuntu - as a result it can be worked around by
manually installing the native 64-bit adobe flash plugin from
Public bug reported:
Provide automatic link handling for CVE identifiers back to the Ubuntu
Security team's CVE database (useful when looking at package changelog's
which have security fixes etc).
** Affects: gnome-terminal (Ubuntu)
Importance: Undecided
Status: New
** Attachment
The upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=579859
** Bug watch added: GNOME Bug Tracker #579859
https://bugzilla.gnome.org/show_bug.cgi?id=579859
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Ok so any guidance as to how to proceed - Jeremy do you have a
preference for how this should work? Would you like it to also support
Debian in a similar manner and link to the Debian CVE tracker? In this
case would you prefer runtime detection (via say /etc/os-release) or
compile-time selection
The other option would be to do it "properly" the way upstream want -
ie. to have the user be able to configure their one linkification.
I am happy to rework the patch - is there any interest in carrying this
just in Ubuntu or would the preference be to push it to Debian and get
it into Ubuntu
*** This bug is a duplicate of bug 1784852 ***
https://bugs.launchpad.net/bugs/1784852
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as
*** This bug is a duplicate of bug 1784852 ***
https://bugs.launchpad.net/bugs/1784852
Also wrong duplicate - ignore comment #4 as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
*** This bug is a duplicate of bug 1784852 ***
https://bugs.launchpad.net/bugs/1784852
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 1779637, so it is being marked as such. Please
*** This bug is a duplicate of bug 1784852 ***
https://bugs.launchpad.net/bugs/1784852
Apologies - ignore comment #2 - wrong bug.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
*** This bug is a duplicate of bug 1784852 ***
https://bugs.launchpad.net/bugs/1784852
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 1784852, so it is being marked as such. Please
Ignore comment #2 - I misread bug #1779637 - this bug is distinct from
that.
Can you provide any details as to whether you are using the X or the
Wayland session?
** This bug is no longer a duplicate of bug 1779637
Password visible at login screen
--
You received this bug notification
*** This bug is a duplicate of bug 1779637 ***
https://bugs.launchpad.net/bugs/1779637
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 1779637, so it is being marked as such. Please
This was fixed in upstream commit
https://gitlab.gnome.org/GNOME/gvfs/commit/a23eb6f14eb3cffa1585d4e5e566f779337d1e04
Uncertain whether this qualifies as a security issue - there doesn't
seem to be any real security impact from the bug - so unmarking this as
a security issue now.
** Information
Seems this is a bug in gvfs not properly validating as UTF8 before
calling into glib: https://bugs.exim.org/show_bug.cgi?id=2330#c9
** Package changed: pcre3 (Ubuntu) => gvfs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
@Seb - so there is an autorun.inf in the original tarball which can be
used (I will attach it separately here as well) - and this reproduces
the crash for me - I just copied it to a FAT formatted USB drive,
plugged it in and then in dmesg:
[ 40.361136] gvfs-udisks2-vo[1563]: segfault at
@Seb - also I rebuilt gvfs locally for bionic with that upstream patch
added and can confirm it does not segfault after that - would be happy
to test your SRUd version and confirm it as well if needed.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
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 1769383, so it is being marked as such. Please
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
*** This bug is a duplicate of bug 1769383 ***
https://bugs.launchpad.net/bugs/1769383
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 1769383, so it is being marked as such. Please
I reviewed libcue (2.2.1-2) from disco. This is not a full security audit but
rather a quick gauge of maintainability.
libcue is a library to parse CUE sheets / files (metadata which describes how
tracks of a CD or DVD are layed out). Stored as plain text and commonly have
the .cue extension.
Tested the version from cosmic-proposed in an up-to-date VM and it
failed - looks like this is not actually applied during the build - see
the build log https://launchpadlibrarian.net/398362236/buildlog_ubuntu-
cosmic-amd64.gvfs_1.38.1-0ubuntu1_BUILDING.txt.gz and notice it is never
listed during
Tested the version from bionic-proposed in an up-to-date VM and it
passed
Steps to test locally as follows:
1. Enabled bionic-proposed
2. sudo apt-get dist-upgrade
3. sudo reboot
On next boot with the autorun.inf on a local USB drive:
$ dmesg | grep gvfs
$ apt-cache policy gvfs
gvfs:
Tested the new version in cosmic-proposed on an up-to-date cosmic VM by
inserting a USB drive with the attached autorun.inf and it passes.
Steps to test locally as follows:
1. Enabled cosmic-proposed
2. sudo apt-get dist-upgrade
3. sudo reboot
On next boot with the autorun.inf on a local USB
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1791433
Title:
Path traversal vulnerability
To manage
https://gitlab.gnome.org/GNOME/gnome-shell/issues/460#note_331931 seems
to offer a pretty compelling explanation of why this might be seen
inadvertently.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #460
https://gitlab.gnome.org/GNOME/gnome-shell/issues/460
--
You received
*** This bug is a duplicate of bug 1772791 ***
https://bugs.launchpad.net/bugs/1772791
** This bug has been marked a duplicate of bug 1772791
Lock/login screen displays password in clear text occasionally
** Information type changed from Private Security to Public Security
--
You
** 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 gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1812527
Title:
[bionic][regression] gnome-shell crashes with SIGSEGV in
** Information type changed from Private Security to Public Security
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
>From a security PoV this is basic security by obscurity and effectively
pointless - they are simply XORing each byte with a fixed value and then
base64 encoding it - since the source code is public anyone can easily
find this out and hence easily decode it - the only way to do this
securely would
@gunnarhj - updated packages for ibus are now available in the ubuntu-
security-proposed PPA at https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa
Also I note the bug descriptions lists ibus in Focal as Fix Released -
but the latest version in focal (1.5.21-1~exp2ubuntu2) is the
Public bug reported:
After a recent gnome-shell + yaru-theme update, AppIndicator labels are
now shown aligned with the top of the top bar instead of aligned
vertically centered as previously https://imgur.com/a/jKVP5w9
(This is the indicator-sensors snap, which creates an AppIndicator with
a
Image demonstrating the issue
** Attachment added: "Screenshot from 2020-03-04 21-21-01.png"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1866042/+attachment/5333430/+files/Screenshot%20from%202020-03-04%2021-21-01.png
** Summary changed:
- AppIndicator
@seb128 - I just noticed this - Apport popped up just after login
saying Files (aka nautilus) had crashed - and pointed at this bug
report. This was the first time I have seen it so not sure if it is
reproducible and I didn't take any particular steps to make it occur.
--
You received this bug
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Public bug reported:
Every morning about ~30mins after powering on my focal machine I get
(unprompted) a gnome-shell policykit authorisation popup saying
'authentication is required to install software' - I haven't yet
actually authorised it since I wasn't sure what was causing it, however
I
Attached log output for gnome-software (if there is a better way to
obtain this or more complete logs for gnome-software please let me
know).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
1 - 100 of 138 matches
Mail list logo
