I can confirm this bug. I can't neither set the screen resolution via
the settings nor via kscreen-doctor as well. Scaling works via settings,
but it's not a solution, because not every application works well with
that.
--
You received this bug notification because you are a member of Ubuntu
Bugs
*** This bug is a duplicate of bug 1907878 ***
https://bugs.launchpad.net/bugs/1907878
I am getting DOMAINS in /etc/resolve.conf:
DOMAINS is initialized with "DOMAINS" in `/etc/network/if-up.d/resolved`
and set in /run/systemd/resolve/netif/*
```bash
$ cat /run/systemd/resolve/netif/3
# This
Public bug reported:
Ubuntu 20.04.3 LTS x86_64 fully updated with apt.
My installed packages:
ii pulseaudio 1:13.99.1-1ubuntu3.11
amd64PulseAudio sound server
ii paprefs1.1-1build1
I have a Yoga C940, which is the precursor to the 9i. It has the
soundbar and two speakers under the body of the laptop. Out of the box
the body speakers did't work but there is a special BIOS for the C940
(only) that activates an amplifier for these speakers. I think that
the C940 only has two
it seems that it was already fixed in 5.7.2-2ubuntu1.2
** Changed in: collectd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918667
Title:
collectd disk plug
this commit could be backported and would fix this issue:
https://github.com/Stackdriver/collectd/pull/182/commits/f7b16999c0bf5d61dec559b92a7afba214b06bee
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
after updating a ubuntu 18.04 machine to HWE 5.x kernel the disk plugin
doesnt work anymore.
its seems to be related to
https://github.com/collectd/collectd/issues/2951
the issue was fixed in 5.8.1
** Affects: collectd (Ubuntu)
Importance: Undecided
Status: In
I should maybe add the following detail:
Channel binding, from all I can tell, is only available via TLS (even
conceptually). That is, the issue mentioned in the bug report only
happens when using ldaps.
In certain cases, it is therefore possible to work around the lack of
channel binding by _not
Might have been confusing to write
# kinit
$ export LDAPSASL_CBINDING=tls-endpoint
Both are supposed to be called from the same user. I meant to imply that
an existing, valid ticket in the current user's credential cache is
required for krb5 authentication via SASL in the ldapwhoami step.
--
Yo
Public bug reported:
> Are you uncertain if your issue is really a bug?
Effect is an authentication error. Root case is a "missing feature" (see below)
and requires updating dependencies, downporting.
> If you are certain this is a bug please include the source package the bug is
> in.
It's in
Public bug reported:
Upgradevon18.04auf20.04
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.40
ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18
Uname: Linux 4.15.0-124-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
Crash
Public bug reported:
Version of flowblade (2.4.0.1-2) installed by apt is out of date, please
update to current release version (2.6.0-1 at this time).
https://github.com/jliljebl/flowblade/releases
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: flowblade 2.4.0.1-2
ProcVersionSignature: U
Hello Paride,
thank you for your evaluation of the bug report. I'll try to give you
all the facts to support the process.
In our case the bug is not purely cosmetic. We restrict access for the
read-only community for SNMPv2 in our snmpd.conf to a source host. The host is
defined as a hostname,
Public bug reported:
Sometimes snmpd starts too early in the bootprocess and cannot resolve
hostnames in the access control part of the configuration.
This might be related to the dependencies of the snmpd systemd-unit.
Seems like snmpd should depend on network-online.target, not network.target.
Can confirm this still happens with kernel 5.8.1. While the device is
listed correctly with its full name in bluetoothctl and can be trusted,
the final pairing will not work. syslog will constantly have a
"Refusing" message for the device and the connection:
Aug 12 15:47:25 htpc blueman-mechan
sktop computer.
Sincerely,
Rich Schneider
On 7/20/20 1:22 AM, Chris Guiver wrote:
> Thank you for taking the time to report this issue and helping to make
> Ubuntu better.
>
> I didn't look for your actual issue, but I saw a number of things that
> would have me checking your hard
Public bug reported:
Do not know what is the problem
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15 [modified:
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules:
Cannot reproduce this very issue with the fallback Kernel.
Linux sisc-ws 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
Instead, seeing some issues with nouveau. See attached dmesg output with
older kernel
** Attachment added: "dmesg_5.4.0-33-generic
** Description changed:
After login into the gnome session, the session freezes, either
instantly or after a few seconds ( only mouse is working ). The Oops
does not occur on every startup. After a few restarts, the kernel Oops
- does not occur anymore during the complete
+ does not occur an
Public bug reported:
After login into the gnome session, the session freezes, either
instantly or after a few seconds ( only mouse is working ). The Oops
does not occur on every startup. After a few restarts, the kernel Oops
does not occur anymore during the complete
Dell Perfomance Checks ( incl
Public bug reported:
>From /proc/bus/input/devices:
I: Bus=0018 Vendor=06cb Product=cd97 Version=0100
N: Name="DELL08E1:00 06CB:CD97 Touchpad"
P: Phys=i2c-DELL08E1:00
S:
Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-9/i2c-DELL08E1:00/0018:06CB:CD97.0002/input/input30
U: Uniq=
H: Ha
any update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832304
Title:
SSL socket segfaults during a connect() using a punycode domain
containg a umlaut
To manage notifications about this bug g
I can confirm that the bug was fixed by installing the updated
2.4.29-1ubuntu4.7 package from bionic-proposed. Thank you all for your
help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
@Andreas Hasenack:
Many thanks - the patches from your PPA worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1833039
Title:
18.04/Apache2: rejecting client initiated renegotiation due to openss
Downgrade was not so easy, because apt wanted to remove a heck of a lot of
other packages.
In the end I manually unpacked libsssl1.1_1.1.0g-2ubuntu4.3_amd64.deb and
copied the files over.
-> The problem was fixed.
So indeed the openssl library 1.1.1 caused these issues.
--
You received this bu
Public bug reported:
I am using Apache2 with client certificate authentication.
Since recently (last week) and without any configuration changes, the following
errors occur frequently:
AH02042: rejecting client initiated renegotiation
Client connections are very slow and sometimes it takes more
Public bug reported:
Hey,
yesterday I stumbled across a segfault which is already fixed upstream.
Can you please apply the patch for it?
chs@gw-sss-nb8:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename:
this bug is fixed with
https://github.com/thjaeger/easystroke/commit/7bda4bd9c705413598ee9b534884bc7f23704932
which is in git master, possible other patches mentioned below also
could help:
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.
As master is also
this bug is fixed with
https://github.com/thjaeger/easystroke/commit/d14b2740bf3b0ec867d7a0abe4e1f64fb6687aba
which is in git master
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.
As master is also outdated, you will need to add at least these patches (
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.
possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190
As master is also outdated, you will need to add at least this patch:
https://github.com/thjaeg
this bug is fixed with https://aur.archlinux.org/cgit/aur.git/tree/dont-
ignore-xshape-when-saving.patch?h=easystroke-git
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.
As master is also outdated, you will need to add at least these patches (ubuntu
pac
*** This bug is a duplicate of bug 1771151 ***
https://bugs.launchpad.net/bugs/1771151
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.
possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190
As
It seems like easystroke on ubuntu is still built from 0.6.0 release and
not from master.
possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190
As master is also outdated, you will need to add at least this patch:
https://github.com/thjaeg
It seems like easystroke on ubuntu is still built from 0.6.0 release and not
from master.
possibly related bug is also fixed in master:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1426190
As master is also outdated, you will need to add at least this patch:
https://github.com/thj
--- random-amd642018-10-30 16:08:18.195414933 +
+++ random-armhf2018-10-30 16:08:58.225789786 +
@@ -184,6 +184,11 @@
#ifdef __SSE2__
__m128i _M_state[_M_nstate];
#endif
+#ifdef __ARM_NEON
+#ifdef __aarch64__
+ __Uint32x4_t _M_state[_M_nstate];
+#endif
+#endif
This bug fix causes a regression in Xenial when installing initramfs-
tools in QEMU, since the version of QEMU in Xenial does not support
syncfs():
/bin/sync: error syncing '/boot/initrd.img-4.14.44-v7ooicgsn': Function
not implemented
--
You received this bug notification because you are a memb
You can use this ppa meanwhile
ppa:tomtomtom/filemanager-actions
https://launchpad.net/~tomtomtom/+archive/ubuntu/filemanager-actions
thus, proper debian source packaging already exists, so putting into
repository should be rather easy ;-)
but as debian upstream also does not have the package,
Public bug reported:
Near same problem, but using legacy boot. Would guess that this could
make a difference.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.2
I got something similar and I attach the files you asked for.
sudo apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... failed.
The following packages have unmet dependencies:
glib-networking : Depends: libgl
Public bug reported:
https://github.com/moneymanagerex/moneymanagerex/blob/master/INSTALL.md#linux
sudo apt-get update && sudo apt-get -y upgrade
sudo apt-get -y install git build-essential automake cmake python libwxbase3.0
libwxgtk-webview3.0 libwxgtk-media3.0 libgtk-3-0 libwebkitgtk-3.0-0
li
Thank you,
I am sorry to get back to you so late but i had other things more
pressing.
I attempted to find Fotoxx in the software center and it was not there,
even after doing a typed in search. I like the program so I went to the
developer's site and down loaded it.
Once again,
Thank you,
R
Public bug reported:
I really don't know except the update failed.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: fotoxx-common (not installed)
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: a
Thank you Dave,
I did get it working by some sort of magic that I cant quite explain. It
works and I'm happy.
Thank you for the suggestion though.
Best regards,
Rich S.
On 05/05/2018 03:08 AM, Dave Goldsbrough wrote:
> At a terminal screen have you tried entering the command?
>
> sudo servic
Public bug reported:
I can't make the WIfFI operate Compact Presario V2000
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic i686
NonfreeKernelModules: wl
.tmp.unity.suppor
Public bug reported:
just the errors that are already predicted in
https://help.ubuntu.com/community/ManualFullSystemEncryption/DetailedProcessInstallUbuntu
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubiquity 17.10.10
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
Uname: Lin
Sorry. Mistyped. Read initramfs SETS UP wrong ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752528
Title:
initramfs swretu up wrong swap partition for resuming when zram-config
is active
or blacklist zram
devices as being candidates for resuming?
Yours truly. With great respect. Mr SCHNEIDER
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic x86_64
Apport
Public bug reported:
no further infos
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: grub-common 2.02~beta2-36ubuntu3.16
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: W
Public bug reported:
This issue happened when i tried to update.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.
Bug confirmed, log attached:
Setting up linux-image-extra-4.13.0-26-generic (4.13.0-26.29~16.04.2) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.13.0-26-generic
/boot/vmlinuz-4.13.0-26-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.13.0-26-generic
/boot/vmlinuz-4
Public bug reported:
The new version 4.13.0.19 of Linux-signed-image and linux-image-generic
seem to have a sependency conflict/version mismatch on UEFI systems,
which causes linux-signed-image to try to self-uninstall.
Seems unsafe, because this would take away the Ubuntu UEFI signing
certificat
Amendment to #24
The following solution worked for me for installation:
(see:
https://askubuntu.com/questions/845401/installing-lubuntu-16-10-with-encrytion)
I booted using 17.04 64 bit and did choose the "Try Lubuntu" option from the
boot menu.
>From the desktop I have chosen "start menu" -> "sy
Tried lubuntu-17.04-desktop-amd64.iso on a lenovo yoga 300 several times
using "sudo swapoff --all" before running into error. Thus the error
message changed to auto-partition failed.
At my system the auto-partitioning creates a 1MB partition as first an one as
last partition on disk, which is qu
Public bug reported:
1. Ubuntu 16.04.2 LTS
2. 2.27.1-6ubuntu3.3
3. Nothing
4. An error message stating the package could not be installed popped
up.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
U
I guess this bug is why I can't upgrade my kernel :
( 17.04 + zfs-dracut )
Setting up linux-image-4.10.0-20-generic (4.10.0-20.22) ...
Running depmod.
sh: 1: /usr/sbin/update-initramfs: not found
Failed to create initrd image.
[...]
--
You received this bug notification because you are a member
** Changed in: lxpanel (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1517354
Title:
panel width resets to 150 after logout
To manage notifications about
ckage nvidia-glx-177 177.80-0ubuntu1 [modified: usr/bin
** Changed in: nvidia-graphics-drivers-173 (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/283747
Title:
Public bug reported:
After logging in, an error report dialogue appears with the following error:
package libglewmx1.10:amd64 1.10.0-3 failed to install/upgrade: package
libglewmx1.10:amd64 is already installed and configured
I am running Ubuntu MATE 15.10. What I expected to happen: Log in and
ested ubuntu mate, xubuntu and kubuntu, all have the same problem, did
not Ubuntu though...
Thank you for replying.
Regards
Sergio
On Sat, Oct 17, 2015 at 11:36 PM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Sergio Schneider, the issue you are reporting is an upstr
That is correct, after installation, If I install nvidia drivers the
problem gets solved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1506272
Title:
Missing fonts and flickering font rendering
To
Christopher M. Penalver (penalvch) Absolutely yes, but only after
installation to hd/ssd, no way to make it work in live mode (if so, I
don't know how to do it)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Christopher, just did it:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1506272
Hope it helps, 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/1501658
Title:
10de:1381 [Asus B85M-E] M
Public bug reported:
Nvidia GPU GTX 750, Intel CPU, running ubuntu mate daily ISO 2015-10-14
in live mode
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ub
Just tried today's (oct/14) daily live ISO of Ubuntu MATE in live mode,
problem persists and as mentioned above if I change fonts to VRGB it
gets better, but some windows do lose/flicker fonts/characters.
Nvidia GPU GTX 750
--
You received this bug notification because you are a member of Ubuntu
@Martin
Ok, I tried the latest Ubuntu Mate ISO from oct 02/2015
Same problem in live mode... tweaked some settings (rgb, vrgb, etc... ) VRGB is
better but not perfect at all...
Installed to SSD and boot, fonts still messed, installed Intel microde,
rebooted and problem persisted. Another reboot,
Same problem here in live usb mode, tested kubuntu, ubuntu-mate and xubuntu
My rig: Home built desktop, mobo gigabyte, 32GB RAM, Nvidia GTX 750 ti, intel
i7, ssd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
*** This bug is a duplicate of bug 283662 ***
https://bugs.launchpad.net/bugs/283662
** This bug has been marked a duplicate of bug 283662
no login promt at "recovery mode"-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
is but I'm
still learning and I am unfamiliar with Kernels.
Sincerely,
Rich Schneider
On 07/26/2015 09:16 AM, Christopher M. Penalver wrote:
> Richard Schneider:
>
> Could you please test the latest upstream kernel available from the very
> top line at the top of the page (the relea
Hi,
Upon Israels reply I did a random search, sharing the same bug ever
since, so I was able to find this workaround, which solved it for me:
http://askubuntu.com/questions/624797/problem-with-battery-indicator-in-
lubuntu-15-04
It basically updates xfce power manager inlcuding plugins to 1.5.0.
Public bug reported:
Occurs after trying to install fglrx on a fresh install of Ubuntu 15.04.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
.tmp.unity.suppo
Public bug reported:
Fresh install 15.04, updated everything(pre-release) via software
updater, download the AMD driver and install it but this problem appears
and I'm not able to log in, the log in screen appears but I never see
the desktop... I'm even not able to use Ctrl + Alt + F2 or any other
I might also add that I replaced my keyboard with a new one with no
improvement. A USB plug in keyboard is the only way I can use this
laptop computer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/146
I went through more nonsense trying to update the bios to version 3.60
but I finally succeeded and reinstalled Ubuntu 14.04. Updating bios 3.50
to 3.60 did not improve anything. I downloaded Ubuntu version 15.0?
hoping that it may make some difference. It did not. With version 13 of
Ubuntu my keybo
I also still have this on 15.04. I have removed all non-Ubuntu
repositories but to no avail.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1211511
Title:
update-manager hides but wants to install ig
No action yet that I can see. Does anyone know how to get this patch
looked at? The current setup with its 5 second delay is getting
annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210898
No action yet that I can see. Does anyone know how to get this patch
looked at? The current setup with its 5 second delay is getting
annoying.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312641
Public bug reported:
I can't describe it more than the keyboard startedacting
weird
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-54.91-generic 3.13.11-ckt20
Uname: Linux 3.13.0-54-generic i686
.tmp.unity.support.te
The problem started after the last set of updates less than one week
ago.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1465392
Title:
Odd Keyboard responses
To manage notifications about this bug
Public bug reported:
I try to update ubuntu to the new release ubuntu 15.04
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: ubuntu-release-upgrader-core 1:14.10.10
ProcVersionSignature: Ubuntu 3.16.0-38.52-generic 3.16.7-ckt10
Uname: Linux 3.16.0-38-generic x86_64
NonfreeKernelModules: fglr
i have a lenovo t450s and following kernel:
3.16.0-38-generic #52~14.04.1-Ubuntu SMP Fri May 8 09:43:57 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
now the trackpad buttons working well
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Hello Paul,
I got my problem solved, on my side it wasn't a bug. It turned out, my problem
was a ppa that made me use a 16bit ImageMagick. In my case it was
ppa:dhor/myway which I used because of rawtherapee. Once I removed uninstalled
ImageMagick/Octave. removed the ppa and reinstalled octave
OK, done.
Hopefully this will get picked up faster than your patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312641
Title:
Removable drives and media do not automatically mounted at boot
To
Created attachment 6191
Try to get GVolume right away and only if that fails wait for 1 second
This should change the total delay from 5 seconds per partition to at
most 1 second for an entire physical device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I see that 0.8.1 has your patch.
I think that better than waiting 1 second would be to try immediately
and only then wait for a bit. I modified the code accordingly, ending
up with
static gboolean
tvm_block_device_mount_volume (TvmContext *context, GVolume *volume)
{
GMountOperation *mount_op
I see that 0.8.1 has your patch.
I think that better than waiting 1 second would be to try immediately
and only then wait for a bit. I modified the code accordingly, ending
up with
static gboolean
tvm_block_device_mount_volume (TvmContext *context, GVolume *volume)
{
GMountOperation *mount_op
https://bugzilla.xfce.org/show_bug.cgi?id=9193#c14
doesn't work reliably for me. It may be that it doesn't help at all,
except to cause the race condition to sometimes come out the "right"
way.
The problem is still active with Thunar 1.6.6 and thunar-volman 0.8.0.
I'm going to try to add some pa
My patch that tries to get the volume up to three times, with a 1-second
delay between each time, hides the problem successfully.
However, a better solution would be to have thunar-volman only called
when the volume has been set up. This is known, as the volume has to be
set up for the icon to ap
OK, done.
Hopefully this will get picked up faster than your patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210898
Title:
Removable drives and media not automatically mounted/listed
To mana
Created attachment 6191
Try to get GVolume right away and only if that fails wait for 1 second
This should change the total delay from 5 seconds per partition to at
most 1 second for an entire physical device.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
https://bugzilla.xfce.org/show_bug.cgi?id=9193#c14
doesn't work reliably for me. It may be that it doesn't help at all,
except to cause the race condition to sometimes come out the "right"
way.
The problem is still active with Thunar 1.6.6 and thunar-volman 0.8.0.
I'm going to try to add some pa
My patch that tries to get the volume up to three times, with a 1-second
delay between each time, hides the problem successfully.
However, a better solution would be to have thunar-volman only called
when the volume has been set up. This is known, as the volume has to be
set up for the icon to ap
Encountered exactly the same problem while running UpdateManager.
How can I resolve this issue?
Right now I am stuck, and cannot get either forward (with upgrading packages)
or backward (remove openjdk-7-jdk), because of unmet dependencies in the
package database.
Any hints are appreciated. Tha
m> wrote:
> Diogo Schneider, just to clarify,
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1408821/comments/6
> you weren't asked to commit bisect back to Lucid. Instead, what is being
> asked is a reverse commit bisect, in order to find the good/fix commit
> issued be
, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Diogo Schneider, this is not Fix Committed as defined in
> https://wiki.ubuntu.com/Bugs/Status . Despite this, the next step is to
> fully reverse commit bisect from kernel 3.13 to 3.19-rc3 in order to
> identify the last ba
es or should I remove it at some point?
Thanks,
Diogo
On Fri, Jan 9, 2015 at 7:35 PM, Diogo Schneider
wrote:
> Hi, Cristopher!
>
> I think I have found the problem. Please follow with me the installation
> process:
>
> diogo@CQ43:~/Downloads$ ls
> linux-heade
I actually don't even think my connection will work at all after
rebooting.
Cheers,
Diogo
On Fri, Jan 9, 2015 at 9:52 AM, Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Diogo Schneider, thank you for reporting this and helping make Ubuntu
> better. Could
Public bug reported:
This same Wi-Fi adapter used to work very well with Ubuntu 9 or 10, I
can't remember... but now it just drops some packages and sometimes the
whole connection every now and then.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-32-generic 3.13.0-32.57
Public bug reported:
system starting with this error
ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.113-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
A
It also helps to remove "splash" from the kernel line (for example in
/etc/default/grub and rerun update-grub). Then you lose the splash screen but
can normally enter the password.
That's ofcourse just a workaround, since the splash screen is kind of integral
to the user experience imho. Without
This bug affects me too. However I don't think it is related to the kernel.
Reason for me to say this:
One of my machines had some strange problems during the upgrade from 14.04 to
14.10. The result was, that I was still on kernel 3.13 after the upgrade. When
this problem with the crypto prompt
1 - 100 of 669 matches
Mail list logo
