Backblaze sdk is compatible with Python 3.10 since release 1.13, 21 Oct 2021.
https://github.com/Backblaze/b2-sdk-python/commit/cd64eafdcf60e6f19d90e7d6fafeff4234850b8d
Thank you for breaking my backup...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
There is a patchset in a comment in the upstream bug report that makes it work
for me:
https://github.com/home-sweet-gnome/dash-to-panel/issues/1581#issuecomment-1068981549
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After upgrade of gjs to 1.71.90-1, `dash-to-panel` extension cannot be
enabled. Error message reads
Object 0x3adcf2e07098 is not a subclass of GObject_Object, it's a Object
There is an upstream bug report about this issue:
Started to happen to me on impish, possibly after firefox upgrade to
94.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915449
Title:
XWayland hangs at 100% of CPU causing gnome-shell to hang
To
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929471
Title:
Shim apparently fails to run fwupd64 (hirsute
Installed shim-signed_1.49+15.4-0ubuntu7_amd64.deb from impish on
hirsute,
Verified that it works, I was able to install all pending firmware
updates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I could try to test the suggested change...
I understand that I would need to
- generate a key pair
- roll the public key into bios
- build the shim
- sign the shim with the private key
- set a boot entry with the new shim and updater as its parameter
- try to boot via this new boot entry
Is
Public bug reported:
I am running hirsute on Thinkpad X1 Carbon gen 7. Fwupdmgr used to work
on groovy. Now, fwupdmgr detects new firmware, successfully places the
.cap file in /boot/efi/EFI/ubuntu/fw/, successfully sets efi "next boot"
to 2 which is "Linux-Firmware-Updater", but on reboot, there
I confirm that with libc6 version 2.33-0ubuntu4 installed, postfix works
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916541
Title:
smtp "fatal: unknown service: smtp/tcp", probably after
I confirm that after upgarading lvm2 to 2.03.11-2ubuntu3 from -proposed,
the hook file has correct permissions, and resulting initrd is bootable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915579
Public bug reported:
after a recent (yesterday/today) upgrade of hirsute, it could not boot
from LUKS root, dropping to inirtamfs. Investigation showed that `lvm`
binary is not present in initramfs generated by initramfs-tools. When I
ran `initrmfs-tools` by hand with `-v` option, I noticed the
Thanks Paride,
I am glad that you could reproduce it, and it's not like either I or my system
is crazy :)
I noticed something that may or may not be relevant. I have another
machine with hirsute, that was purchased a year+ ago and has undergone
less package upgrades: mail delivery _worked_
Hello @sergiodj,
> Could you perhaps provide the configuration files you used to do that?
My complete configuration is included in the tar attached to this
ticket.
> please make sure that your Hirsute system is up-to-date
Yes, updated daily, _plus_ by hand right before the investigation.
Note
I did some more investigation, and did not find an explanation, but I am
writing it here to maybe save somebody else some effort.
Postfix uses normal(?) `getservbyname(service, protocol)` in the file
src/smtp/smtp_connect.c line 363:
if ((sp = getservbyname(service, protocol)) == 0)
** Changed in: postfix (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1916541
Title:
smtp "fatal: unknown service: smtp/tcp", probably after libc upgrade
Hello @lucaskanashiro,
it may work differently in a container because the problem may be
triggered by a combination of libc components and possibly the kernel
(only a speculation). I can reproduce the problem on another hirsute
machine, postfix was never used there. I `dpkg-reconfigure`d it as a
Public bug reported:
On hirsute, on Jan 20, postfix stopped sending outgoing mails with the
error
Feb 22 23:35:18 pccross postfix/smtp[9582]: fatal: unknown service:
smtp/tcp
There were no changes in the system other than daily upgrades.
Strace shows that `smtp` process (while chrooted), after
I understand that it's fixed in the mainline quite a while ago, no?
Don't get it why is "verification-needed" now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865570
Title:
suspend only works
I had this happen again about a week ago, though it happens very rarely
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881505
Title:
Sound w/SOF driver sporadically fails on Lenovo Carbon X1
** Bug watch added: github.com/fwupd/fwupd/issues #2169
https://github.com/fwupd/fwupd/issues/2169
** Also affects: fwupd via
https://github.com/fwupd/fwupd/issues/2169
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
On Lenovo ThinkPad Carbon gen 7, the default EFI boot list looks like
this:
BootCurrent: 0001
Timeout: 0 seconds
BootOrder: 0001,0019,001A,001B,001C,001D,001E,001F,0020,0021,0022,0023,0024,0002
Boot0001* ubuntu
Public bug reported:
Now and then, the notebooks stops producing any sound, and program that
try to use sound output freeze for many seconds. There is a repeating
sequence on messages in `dmesg`:
[116525.402057] sof-audio-pci :00:1f.3: error: ipc timed out for 0x8001
size 120
I was encountering this problem before and had to fall back to the
legacy driver (that works but without microphone). Now I was able to
blacklist legacy driver again, and got SOF working, including the
microphone.
focal on Carbon X1 gen7
linux-firmware 1.187
kernel 5.4.0-28-generic
I can confirm
Public bug reported:
Applications using this module crash with
File "/usr/lib/python3/dist-packages/b2sdk/b2http.py", line 13, in
import arrow
ModuleNotFoundError: No module named 'arrow'
because python(3)-arrow is not automatically installed as a dependency
for python(3)-b2sdk.
**
Thanks Mario. The theory makes sense.
I _think_ that after boot with BootNext=, entry disappeared and
BootCurrent was 0001 (but I cannot be 100% sure as I did not save the config at
the time).
My firmware _did_ respect BootNext when it was set to 0002, and it was
the only updater
Before raising the issue with fwupdmgr, why did not shim load the
updater from the entry as instructed by BootNext? Configuration
looks strange, but legit to the eye. Does shim or firmware check for
duplicate entries? Does shim or firmware not allow to use entry 0?
Right now, I am unsure
I did not change any bios settings since upgrade from eoan, and firmware
update worked in eoan.
But I found something interesting.
In "normal life" my efi configuration looks like this:
BootCurrent: 0001
Timeout: 0 seconds
BootOrder:
crosser@journex:~$ apt policy shim-signed
shim-signed:
Installed: 1.40+15+1533136590.3beb971-0ubuntu1
Candidate: 1.40+15+1533136590.3beb971-0ubuntu1
Version table:
*** 1.40+15+1533136590.3beb971-0ubuntu1 500
500 http://ftp.tu-ilmenau.de/mirror/ubuntu focal/main amd64 Packages
Could it be that newer "bad" versions continue to linger on ubuntu
mirrors?
Julian, can you post here, which version is known to work and is going
to the official distro?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I see 1.40+15+1533136590.3beb971-0ubuntu1 in the main focal repo, and
15+1552672080.a4a1fbe-0ubuntu1 in -proposed. Neither of them load
fwupdx64.efi for me?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Using the kernel package from -proposed makes suspend work normally as
well.
Linux journex 5.4.0-20-generic #24-Ubuntu SMP Mon Mar 23 20:55:46 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
Though I guess that 5.4.0-20 uses the "workaround", and it may be better
to apply the "proper fix" from comment
@mapengyu, I've rebuilt e1000e.ko with your patch applied to 5.6.0-rc5
tree, and suspend works normally for me:
Linux journex 5.6.0-rc5+ #2 SMP Sun Mar 15 00:09:19 CET 2020 x86_64
x86_64 x86_64 GNU/Linux
First suspend:
[ 66.578525] PM: suspend entry (s2idle)
[ 66.582870] Filesystems sync:
@Julian, of course I understand the implications. Thank you for the pointer.
(Is it an option to revert to previous signed shim for the release? It did
work.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If there is an updated package available, I am willing to test it on my
system..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load
I can confirm that suspend works normally with the kernel from comment #16
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865570
Title:
suspend only works once on ThinkPad X1 Carbon gen
To check the theory from comment #13, I built kernel from mainline at
tag v5.6-rc5. Out of the box, it behaves the same way as all recent
kernels: suspend works only the first time. I could not revert commit
f15bb6d (there were later changes), instead I commented out the calls to
JFYI, with the current "proposed" kernel behaviour is the same (problematic):
5.4.0-18-generic suspend works only the first time
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865570
Title:
suspend
> 5.4.0-16/17 are abandoned for issues of s2idle, please ignore it.
I do not understand that.
With the current "official" kernel, the problem still exists:
5.4.0-17-generic suspend works only the first time
The only kernel that works for me is 5.4.24-050424-generic from
@kaihengfeng, unfortunately that does not work.
I could not find time to do git bisect (each kernel build takes a long time),
but it would not help if I did. I did a "bisect" over the packages in
https://kernel.ubuntu.com/~kernel-ppa/mainline/. The problem is, between the
version with working
Could the culprit be enabled "wake on LAN" functionality of e1000e, that
was not enabled in 5.3?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865570
Title:
suspend only works once on ThinkPad X1
5.6.0-050600rc4-generic
Same behaviour:
First time works:
[ 122.113542] PM: suspend entry (s2idle)
[ 122.118823] Filesystems sync: 0.005 seconds
[ 122.120954] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 122.12] OOM killer disabled.
[ 122.123334] Freezing remaining
To clarify my comment #1: update files are installed in
/boot/efi/EFI/ubuntu/fw, but on reboot, there is no sign of fwupdx64.efi
ever running, boot process goes straight to grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think that it happens to me, and it's regression going from eoan to
focal. Firmware updates are downloaded and installed, and even if I set
BootNext by hand, it is bypassed.
Linux-Firmware-Updater looks suspicious to me:
# efibootmgr -v|grep Linux-Firmware-Updater
Boot0002*
Opened as bug 1865570
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861462
Title:
Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume
To manage notifications about this bug go to:
** Summary changed:
- suspend only works once on ThnkPad X1 Carbon gen 7
+ suspend only works once on ThinkPad X1 Carbon gen 7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865570
Title:
suspend
Public bug reported:
5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only
once* after boot. On subsequent attempts, when the lid it closed,
backlight and wifi are turned off, but system does not suspend.
First successful suspend:
[ 147.413295] PM: suspend entry (s2idle)
[
To add to #11:
5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once*
after boot. on subsequent attempts, when the lid it closed, backlight and wifi
are turned off, but system does not suspend.
First successful suspend:
[ 147.413295] PM: suspend entry (s2idle)
[
Correction: setting `snd_hda_intel.dmic_detect=0` does make
snd_hda_intel driver work (without microphone, as before).
However SOF driver that worked in eoan (5.3) kernel _with upstream SOF
firmware_ does not work in focal (5.4) kernel. Microphone _did_ work
with SOF.
--
You received this bug
Sound does not work for me on ThinkPad X1 Carbon 7gen with the same messages in
dmesg.
Specifying 'snd_hda_intel.dmic_detect=0' does not change behaviour on 5.4.0-16,
and if I specify it with 5.4.0-14, it hangs a few seconds after boot. Sound
worked on eoan (kernel 5.3.0-40).
--
You received
I confirm that suspend does not work with 5.4.0-14-generic and does work
with 5.4.0-16-generic on Thinkpad X1 Carbon 7gen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861462
Title:
Lenovo
Indeed. When I thought that I switched to distro-provided package a few
years back, I forgot to update the path in my cron script. Sorry for the
confusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
After yesterday's upgrade, librsync2 is 2.0.2-1, it's shared object name
is
/usr/lib/x86_64-linux-gnu/librsync.so.2
but duplicity's _librsync.so wants librsync.so.1:
etc/cron.daily/dbackup:
Traceback (most recent call last):
File
*** This bug is a duplicate of bug 1839661 ***
https://bugs.launchpad.net/bugs/1839661
** Tags removed: amd64
** Tags added: need-duplicate-check regression
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Regression after upgrade disco -> eoan, booted from btrfs disks. Worked
normally before upgrade, cannot install grub after upgrade. Ended up
with non-bootable system, had to plug an old disk exclusively to put
/boot there.
--
You received this bug notification because you are a member of Kubuntu
Scratch my previous comment #3, replacing fast_tls does help!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832653
Title:
ejabberd fails to work after upgrade of openssl to v1.1.1 in Ubuntu
Replacing /usr/lib/erlang/lib/p1_tls-1.0.20/ contents with the modules
built from git master (Release 1.1.1 from May 23 2019) and adding
`no_tlsv1_3` did not work for me (18.04.2). I still get
Failed to secure c2s connection: TLS failed: client renegotiations
forbidden
with both Gajim
I am ready to accept the reasoning behind treating Gmail as a special
case, and disallowing the use of user-specified folder as the trash
folder.
But I think that lying to the user is unacceptable. If user's selection
of the trash folder is going to be ignored, the user must be told so.
Either by
I, too, had this bug manifested on clean Ubuntu without PPAs and without
AMDGPU.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767312
Title:
[radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong
I am not sure that the suggested patch is a good fix for the problem.
As I understand it, with the patch, when the currently active destination
becomes unavailable, new destination is chosen on the basis of its priority.
Now consider my own use case:
I have S/PDIF and Analog outputs on the chip,
(In reply to Tanu Kaskinen from comment #22)
> I believe PulseAudio 9.0 will handle your use case well. Please report back
> if it doesn't.
It does not.
Version: 1:9.0-2ubuntu2
Same behavior: after plugging and unplugging the headset some nonexistent
device becomes active, and I have no sound
(In reply to Tanu Kaskinen from comment #24)
> Do you happen to have the audio settings application open? If you do, it can
> mess up the device selection:
> https://bugzilla.gnome.org/show_bug.cgi?id=762932
It happens when audio control application running and not running
likewise, but desktop's
The problem is in apparmor configuration:
```
audit: type=1400 audit(1524780087.048:210): apparmor="DENIED"
operation="file_mmap" profile="/usr/sbin/ejabberdctl//su"
name="/usr/lib/erlang/p1_pam/bin/epam" pid=25519 comm="epam" requested_mask="m"
denied_mask="m" fsuid=0 ouid=0
```
`mmap`
Public bug reported:
I try to switch from jabberd2 to ejabberd and I need PAM authentication.
I have freshly installed `ejabberd` 18.01-2 and `erlang-p1-pam` 1.0.3-3
packages on bionic, and I enabled PAM authentication in
`/etc/ejabbed/ejabberd.yml`:
```
##
## Authentication using PAM
##
** Description changed:
Xenial 16.04.3 LTS ships with jabberd2 version 2.3.4-1ubuntu2 (as of
this report). This version is vulnerable to CVE-2017-10807, namely it
allows "anonymous" SASL authentication even when that option is switched
off in the configuration:
```
Feb 06 13:34:24
The problem still exists in zesty (despite is says "fix released" in a
comment above).
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1521987
Title:
Sound is not automatically
Still happens in zesty.
May be a duplicate of the bug 1521987
** Tags added: zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563307
Title:
Pulseaudio keeps enabling optical output
To manage
I experience this on Zesty, on an always-on machine, that however relies
on DHCP for network configuration.
I would argue that this is an upstream bug, or if you want a design
flaw.
It is perfectly normal for resolv.conf to change at arbitrary moments.
Examples are VPN and alternative redundant
Public bug reported:
Grafical OS installer just showed the window with a message that it
crashed, without any details.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
Public bug reported:
As of xenial, there is no more bluetooth panel indicator, nor settings
entry. It is not possible to use bluetooth devices. I used bluetooth
headset successfully under Ubuntu 15.10 with cinnamon, and I can use it
now with 16.04 if I log into Unity.
ProblemType: Bug
On my Lenovo X200s digital audio output does not even exist, put it is
present in the sound settings, and every time I plug in and then pull
out the headset, sound output switches to S/PDIF instead of internal
speakers, and I do not hear sound at all. I guess it is the same error.
--
You
As a sidenote, talkplugin is still needed for Firefox users (I don't
know why, Firefox has fully functional WebRTC now, but there you go).
Last published plugin package is of April 2015.
In the long term, it would make sense to modify upstream apt to clearly
distinguish between the problems that
I've opened Bug #1562733 about failed updates due to "No Hash entry in
Release file ... which is considered strong enough for security
purposes"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1558331
Public bug reported:
Since xenial updated the requirements for the strength of PGP signatures
of packages, packages from some repositories are no longer updated. Apt-
get update reports these errors:
E: Failed to fetch http://[...]/Release No Hash entry in Release file
Public bug reported:
Default Cinnamon on vivid (2.2.16-5ubuntu1) does not have Network
Settings in the System Settings. Network panel applet has entries for
Network Settings and Network Connections. The latter opens Gnome
applet (that works). The former opens top System Settings as shown on
the
Public bug reported:
Starting from verstion 34.0, Firefox, including Ubuntu build thereof, supports
WebRTC based voice/video communication feature named Hello:
https://support.mozilla.org/en-US/kb/firefox-hello-make-receive-calls-without-account
This feature works in Ubuntu build, except
I'd like to point out that the description of the bug is inaccurate.
When networkmanager uses dnsmasq, resolv.conf should not be updated when
new dns servers must be used. Instead, networkmanager needs to update
dnsmasq's configuration. And it does not do that, which is a problem.
Proper
I'd like to point out that the description of the bug is inaccurate.
When networkmanager uses dnsmasq, resolv.conf should not be updated when
new dns servers must be used. Instead, networkmanager needs to update
dnsmasq's configuration. And it does not do that, which is a problem.
Proper
Public bug reported:
In the (upstream debian) debian/rules, build flags are defined as such:
DEB_SETUP_GHC_CONFIGURE_ARGS := -fruntimelist -fcreate
The flag -create is false in the original cabal. Turning it on
creates dependency on conduit and most importantly on idna. In great
majority of
Still happend on Trusty.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821233
Title:
indicator-weather crashed with AttributeError in
export_location_details(): Location instance has no attribute
Confirming fixed in mainstream trusty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
[regression] on login screen, monitor stays on forever
To manage notifications about this bug go
@Ted, I am not convinced that you are re-assigning the blame correctly.
I have no 13.04 to compare, but I believe that if the kernel (setterm) blanking
timeout affected the X screen in 13.04, that was probably a bug rather than a
feature. X blanking is controlled by the builtin screensaver
Robert, my observations show that the problem is not that proper setting
are *not applied*, but that they are *overridden* with wrong values
afterwards.
(It conceivable though that g-s-d may be applying the wrong values
after my display-setup-script has applied the right ones. Can you tell
where
I've found something that may be useful both for diagnosis and as a
workaround.
If you define a display-setu-script in the lightdm configuration, like
this:
[SeatDefaults]
display-setup-script=/path/to/display-setup.sh
and put this command in the display-setup.sh:
xset dpms 120 125 130
this
@aperomsik, I am not a developer, I just made and observation in the
hope than someone takes a look at how it was fixed in 2.0.14 perhaps
backports it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This problem has been fixed in the recent build 2.0.14-20131215040026 in
gwendal-lebihan ppa.
(http://ppa.launchpad.net/gwendal-lebihan-dev/cinnamon-nightly/ubuntu/)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am non @Jason, but I've set org.gnome.desktop.wm.preferences focus-
mode 'sloppy' and then killed gnome-settings-daemon. It got restarted,
and the 'sloppy' setting stayed as I've set it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Sebastian, it is weird, now that I am paying attention, I realise that
it is not resetting on every login, and I think at least once it got
reset in the mid-session, without obvious provocation (I was not editing
any other settings or something).
--
You received this bug notification because
cinnamon does indeed start after installing the -proposed
(1.7.4-2ubuntu4.1).
It is still not usable due to that other error (only launchers in the
panel work, clicking on any other applet hangs the desktop, and no mouse
and keyboard events are delivered to the applications).
Anyway this
Public bug reported:
Now that bug #1180538 is fixed, cinnamon session can be started.
Everything operates normally until you click on any of the native
panel applets. Clicking on launchers work as expected, and so is
clicking on the application icons docked in the notification area (such
as
typo: I was referring to the Bug #1180638, not 1180538, sorry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248414
Title:
saucy regression: after clicking on any panel applet, keyboard/mouse
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1248414
Title:
saucy regression: after clicking on any panel applet, keyboard/mouse
input lost
To manage
I opened Bug #1248414 for the problem of keyboard/mouse input not
working after you click menu or other panel applet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180638
Title:
blank desktop at
** Description changed:
- Now that bug #1180538 is fixed, cinnamon session can be started.
- Everything operates normally until you click on any of the native
- panel applets. Clicking on launchers work as expected, and so is
- clicking on the application icons docked in the notification area
I can confirm that since some time ago (perhaps 12.10 or maybe before
that), unity gsettings are being reset on every login.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1112061
Title:
unity
Public bug reported:
I am not sure which package sould be responsible for that, probably
either xorg-server or lightdm.
Previously, up to raring, when you left the computer alone while it was
showing the login screen (lightdm in my case), the monitor would turn
off after five or ten minutes.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1245474/+attachment/3894058/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: LightdmGreeterLog.txt
https://bugs.launchpad.net/bugs/1245474/+attachment/3894059/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: LightdmGreeterLogOld.txt
https://bugs.launchpad.net/bugs/1245474/+attachment/3894060/+files/LightdmGreeterLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1245474/+attachment/3894061/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245474
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1245474/+attachment/3894063/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1245474
Title:
saucy
1 - 100 of 255 matches
Mail list logo
