Not a bug
** Changed in: xrdp (Ubuntu)
Status: New => Invalid
** Converted to question:
https://answers.launchpad.net/ubuntu/+source/xrdp/+question/700604
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See https://github.com/neutrinolabs/xrdp/issues/1723
Define the manager, guess this is the mimimal:
cat .xsessionrc
export GNOME_SHELL_SESSION_MODE=ubuntu
export XDG_CURRENT_DESKTOP=ubuntu:GNOME
** Bug watch added: github.com/neutrinolabs/xrdp/issues #1723
Public bug reported:
When logging in via RDP (xdrp) the buttons minimize and maximize are
missing at the top of each window (left of the destroy cross which is
available at the top-right).
The window color scheme also is light-grey, not the default Ubuntu 20.04
dark-grey.
The destroy button
I think I'll steer away from systemd-resolved
1) it does not favor my primary nameserver (after a switch it'll not switch
back, but continue any failover server)
2) in the end it can even use a nameserver which I have not provided (which is
set by the packagebuilder)
Reading into some threads
192.168.178.1 was defined as secondary nameserver on kvm1804 within
01-netcfg.yaml (ubuntu 18.04).
The primary nameserver is just operating properly. I do not see any
reason why systemd-resolved would not target this primary nameserver,
let alone target something external to me at all.
In case
For completeness, 01-netcfg.yaml for machine kvm1804
** Attachment added: "network configuration for machine kvm1804"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890903/+attachment/5403427/+files/01-netcfg.yaml
--
You received this bug notification because you are a member of
I've now got one instance with this condition again.
>From what I can see from the logs is that systemd-resolved started using some
>other DNS server:
First one in my network where I do not have control over (ipv4: 192.168.178.1 ,
somehow it turned up with this fairly correct address : my
On 4.15.4 I see a lot of:
Feb 21 15:43:31 localhost kernel: [18401.483078] pcieport :00:1d.6: AER:
Corrected error received: id=00ee
Feb 21 15:43:31 localhost kernel: [18401.483095] pcieport :00:1d.6: PCIe
Bus Error: severity=Corrected, type=Data Link Layer, id=00ee(Transmitter ID)
Feb
Public bug reported:
There are still occurrences of this service breaking down.
At some moment the service just stops working correctly and is not able
to recover.
I can reset the service by restarting it:
systemctl restart systemd-resolved.service
I've also tried to set the caching off,
This has apparently just been fixed in Debian, can we copy their fixes?
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879741 .
** Bug watch added: Debian Bug tracker #879741
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879741
--
You received this bug notification because you are
Public bug reported:
Unable to generate certificate request targeting new_oids policy.
It used to work on this machine, looks like openssl got updated just few
days ago: 12-06-2019
The command and exit result:
gge@itstools-04:~/ssl_ownca/direct_1$ openssl req -new -key direct_1.key -out
Hi,
Is fixed for me in 4.15.0-46 Ubuntu 18.04.2 LTS \n \l
gge@jasperserver:/opt$ uname -a
Linux jasperserver 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
I reverted back to 4.15.0-20-generic for proper java operations
gge@jasperserver:~$ java -version
java version "1.8.0_191"
Java(TM) SE Runtime Environment (build 1.8.0_191-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.191-b12, mixed mode)
with kernel
And here's another one... I'm in Ubuntu 18.04, and Apache 2.4 and cURL
can not be installed at the same time.
apache2-bin depends on libcurl3
curl depends on libcurl4
:-(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On the server the docker.service is run.
Sometimes after reboots it hands down a default resolv.conf to docker
domains (8.8.8.8 and 8.8.4.4 if I'm correct) and NOT our local
resolv.conf (which is generated from /etc/network/interfaces).
It looks like a race condition
On 4.15.4 I see a lot of:
Feb 21 15:43:31 localhost kernel: [18401.483078] pcieport :00:1d.6: AER:
Corrected error received: id=00ee
Feb 21 15:43:31 localhost kernel: [18401.483095] pcieport :00:1d.6: PCIe
Bus Error: severity=Corrected, type=Data Link Layer, id=00ee(Transmitter ID)
Feb
Applied to 4.14.14. Offload:
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
rx-vlan-offload: on
tx-vlan-offload: on
dd | sha1sum loop:
742462292c76189f63fc3e7af1acc9dec56c0a8d -
742462292c76189f63fc3e7af1acc9dec56c0a8d
Applied to 4.14.14. Offload:
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
rx-vlan-offload: on
tx-vlan-offload: on
dd | sha1sum loop:
742462292c76189f63fc3e7af1acc9dec56c0a8d -
742462292c76189f63fc3e7af1acc9dec56c0a8d
And just to illustrate my point, on 4.14.0 vanilla:
while true; do
dd if=/nfsmount/debian-live-9.1.0-amd64-xfce+nonfree.iso bs=16M iflag=direct
2>/dev/null | sha1sum; done
With rx offload on (default):
489ed92b17aa9a4582899356d3123621b5d92189 -
742462292c76189f63fc3e7af1acc9dec56c0a8d -
This is happening even on my 9560 with 4.13.9 vanilla; when running a
background rsync backup job, packages downloaded in a Debian docker
build frequently do not match their checksum and need multiple runs to
succeed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi,
I've reported this upstream
(https://bugzilla.redhat.com/show_bug.cgi?id=1413106), and this is not a
bug: thin-provisioning should be used. Snapshots defined on thin-
provisioned LV's show good characteristics.
Gerben
** Bug watch added: Red Hat Bugzilla #1413106
https
of) transaction(s) on a snapshot to
be replayed, not the complete snapshot.
This may need to be reported upstream (which I will do when no other
comments here).
Greetings,
Gerben
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
had a heat-problem on the cpu (dust build-up). If
this bug is cancelled with that in mind I will not object.
Greetings,
Gerben
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651838
Title:
bootup halted
Public bug reported:
Hi,
The bootup process is stopping in 'emergency mode', I have to manually
intervene and perform a 'vgchange -a y' and after 3.5 minutes 6 logical
volumes are active (however I do have 7). Only then I can finalize the
boot process.
Subsequent (all) boots I have to
software.
Greetings,
Gerben
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: virt-manager 1:1.3.2-3ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Mon Oct 10 14:41:39 2016
I can confirm on my side that the whitespace seems to have been the
issue.
I cannot find a single server that spawned on or before the 19th of June
2015.
That brings an end to my search and I suggest to move and close the bug
as this is in fact could be more of a feature request in the direction
Ah, the file itself has nothing wrong with it, but here are my findings:
In /var/lib/dpkg/info/tomcat7.postinst I noticed (as it should) that
/etc/default/tomcat7 was included. In our JAVA_OPTS we just noticed that
there are actual newlines inserted into the definition (as well as in
@Marc Deslauriers (mdeslaur):
-Dcom.sun.management.jmxremote.port=1616
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Djava.awt.headless=true
-XX:+UseConcMarkSweepGC
-XX:+HeapDumpOnOutOfMemoryError
-XX:HeapDumpPath=/dump/
# stat /etc/tomcat7/tomcat-users.xml
File: ‘/etc/tomcat7/tomcat-users.xml’
Size: 1615Blocks: 8 IO Block: 4096 regular file
Device: ca01h/51713dInode: 395363 Links: 1
Access: (0640/-rw-r-) Uid: (0/root) Gid: ( 1001/ tomcat7)
Access: 2016-07-06
Included unattended-upgrades.log
** Attachment added: "unattended-upgrades.log"
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1599378/+attachment/4696380/+files/unattended-upgrades.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Included relevant term.log section
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1599378/+attachment/4696382/+files/term.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Included referenced logfile section
** Attachment added: "unattended-upgrades-dpkg_2016-07-06_06-51-53.656410.log"
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1599378/+attachment/4696381/+files/unattended-upgrades-dpkg_2016-07-06_06-51-53.656410.log
--
You received this bug
If you have not yet upgraded and want to prevent this update, add the
following to your unattended-upgrades file (/etc/apt/apt.conf.d
/*unattended-upgrades or similar)
Unattended-Upgrade::Package-Blacklist {
"tomcat7";
};
--
You received this bug notification because you are a member of
To elaborate a bit on the impact, because this was pushed via Unattended
upgrade as security (!) patch, all our machines, including production
were affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Possibly related issues:
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1556610
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1568836
https://bugs.launchpad.net/ubuntu/+source/tomcat7/+bug/1573954
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
System information:
Description:Ubuntu 14.04.4 LTS
Release:14.04
Kernel: Linux 3.13.0-91-generic
Architecture: x86_64
Issue at hand:
# sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating
Public bug reported:
No details
ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: modemmanager 1.4.8-1
ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
Uname: Linux 3.19.0-18-generic x86_64
ApportVersion: 2.17.2-0ubuntu2
Architecture: amd64
Date: Wed May 20 21:22:59 2015
/simple/efficient as using rsync.
Greetings,
Gerben
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
Date: Sun Sep 14
/simple/efficient as using rsync.
Greetings,
Gerben
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
Date: Sun Sep 14
dmesg shows info for processes 1195 and 4463:
root@dan-09:/var/log# ps auxw | grep X
root 1074 97.5 5.1 591924 422764 tty9Rs+ 09:12 31:32 /usr/bin/X
-core :2 -seat seat0 -auth /var/run/lightdm/root/:2 -nolisten tcp vt9
-novtswitch
root 1195 0.0 7.3 921044 598664 tty7Ds+
Public bug reported:
Using a desktop with two users, it often hangs switching from one to
another. The console comes unresponsive, even text-only (ctrl-alt-f2)
does not show. System itself still runs, I can login over SSH. Process
for Xorg shows one full cpu used.
The system came up from
Public bug reported:
In building a debian package the command dpkg-buildpackage does not hand
parameter -j6 to the make command. The make command keeps getting
called with parameter -j1.
This contradicts with the description for command dpkg-buildpackage.
Warning: next to controlling parameter
Public bug reported:
Hi,
While running virtual clients (kvm) I've noticed the desktop
installations are not shutting down when requested. Any server
installation does properly shutdown. I've installed both ubuntu-13.04
-desktop-amd64.iso and ubuntu-13.04-server-amd64.iso, the server
installation
Public bug reported:
Whent installing 64 bit server 13.04 I noticed I could not log on to the
server directly. Booting the system ends in the server displaying boot
messages, but no login: prompt. None of the other tty screens seem
available.
The system seems to fail any of the tty[1-6] screens
No way to reproduce the bug. The kvm client was moving a lot of data
(22GB newsreading, unpacking).
The kvm host was a clean 12.10 64-bit server install, all updates
performed
I'm having more problems running 12.10, (see Bug 1158995) and frozen
system which I've not reported
The frozen system
Public bug reported:
Hi,
A kernel bug was shown to me on the monitor, the system continued running.
The problem was shown in a process running a KVM client, the client started
resetting a device (windows client: 129: Reset to device, \Device\RaidPort1,
was issued.)
From the syslog I could
** Attachment added: syslog extract
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171957/+attachment/3651773/+files/find01.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1171957
Title:
The whole libvirt installation stopped to be responsive when trying to
shutdown client (reboot in client, and after that force shutdwown
withing virt-manager)
Both virt-manager and virsh list stopped to display results.
Two more kernel BUG messages could be found from syslog (one more file
** Attachment added: two more messages from syslog (of same type, butt
different)
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1171957/+attachment/3651789/+files/find02.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
resize2fs command did not complete at that freeze (so it wat running
at the time).
Gerben
# lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-26-generic 3.5.0-26.42
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic
** Attachment added: photo of text dump
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158995/+attachment/3591092/+files/IMG_4062.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158995
Shutting down cpus with NMI
panic occurred, switching back to text console
[ cut here ]
WARNING: at /build/buildd/linux-3.5.0/arch/x86/kernel/smp.c:123
native_smp_send_reschedule+0x5b/0x60()
Hardware name: To be filled by O.E.M.
Modules linked in:...
** Attachment added:
** Attachment added: photo of text dump
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1158995/+attachment/3591108/+files/IMG_4069.JPG
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1158995
I'm also testing a different package so I've performed a new
installation of Quantal (the third). My previous observation holds.
Please see the new results of bootinfo.
** Attachment added: Results for bootinfo 061, after installing sdc2
Probably apparmor is blocking the executable.
in /var/log/apport.log I can see the line:
ERROR: apport (pid 4224) Fri Oct 26 22:29:35 2012: executable does not belong
to a package, ignoring
When copying qemu-system-x86_64 into /usr/bin
and executing within that directory ( ./qemu-system-x86_64
I'm getting a failure message when starting using virsh start (/usr/bin/kvm is
altered to point to upstream as described)
# virsh start Win7one
error: Failed to start domain Win7one
error: internal error Child process (LC_ALL=C
PATH=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/sbin:/sbin:/bin
Probably apparmor is blocking the executable.
in /var/log/apport.log I can see the line:
ERROR: apport (pid 4224) Fri Oct 26 22:29:35 2012: executable does not belong
to a package, ignoring
When copying qemu-system-x86_64 into /usr/bin
and executing within that directory ( ./qemu-system-x86_64
(and sources.list alterations if needed) available.
Gerben
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1071011
Title:
specific device not available in client (passthrough) with high cpu
load
(and sources.list alterations if needed) available.
Gerben
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1071011
Title:
specific device not available in client (passthrough) with high cpu
load on host, none
to always work is a thing I would like to
know as well)
Greetings,
Gerben
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1069470
Title:
second install of quantal not reached
To manage
Public bug reported:
I've got a specific device which is not always handed down to the kvm
client showing a high cpu load on the kvm host. No cpu load shown in the
client (win7).
A few (two) times I saw this device working properly with no high cpu
usage on the kvm host, but this was broken
Public bug reported:
I've got a specific device which is not always handed down to the kvm
client showing a high cpu load on the kvm host. No cpu load shown in the
client (win7).
A few (two) times I saw this device working properly with no high cpu
usage on the kvm host, but this was broken
It could be the xorg software has a part in this situation. Please do
not follow up this bug anymore, I've reverted to a server installation
and can start clients using the graphics card.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Please make this invalid. I've got the thing running properly under
quantal server including hdmi sound (assign two pci devices). I probably
did something stupid the first time.
Tip: catalyst driver, use custom installation and de-select ccc (from
It could be the xorg software has a part in this situation. Please do
not follow up this bug anymore, I've reverted to a server installation
and can start clients using the graphics card.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please make this invalid. I've got the thing running properly under
quantal server including hdmi sound (assign two pci devices). I probably
did something stupid the first time.
Tip: catalyst driver, use custom installation and de-select ccc (from
Public bug reported:
Within Quantal I cannot start a kvm client using graphical card (amd hd
5450) (anymore). I can start a different client using a differrent
device (usb device)
I've had this machine running under Quantal with the pci device assigned and
was still trying to verify it's proper
lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
root@kvm-03f:~#
apt-cache policy qemu-kvm
qemu-kvm:
Installed: 1.2.0+noroms-0ubuntu2
Candidate: 1.2.0+noroms-0ubuntu2
Version table:
*** 1.2.0+noroms-0ubuntu2 0
500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main
I do see I was able to run the client machine after the last apt update.
It could be some lock persists on the filesystem for that device to be
assigned (persisting over a reboot).
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
Within Quantal I cannot start a kvm client using graphical card (amd hd
5450) (anymore). I can start a different client using a differrent
device (usb device)
I've had this machine running under Quantal with the pci device assigned and
was still trying to verify it's proper
lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
root@kvm-03f:~#
apt-cache policy qemu-kvm
qemu-kvm:
Installed: 1.2.0+noroms-0ubuntu2
Candidate: 1.2.0+noroms-0ubuntu2
Version table:
*** 1.2.0+noroms-0ubuntu2 0
500 http://nl.archive.ubuntu.com/ubuntu/ quantal/main
I do see I was able to run the client machine after the last apt update.
It could be some lock persists on the filesystem for that device to be
assigned (persisting over a reboot).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Two installations of Quantal, no specific /boot partition (/boot
directory is part of private / disk).
In trying to verify certain behaviour in a Quantal installation I
installed a new Quantal in a different partition (scd1 as opposed to
sdb1) and expected the MBR to use the
lsb_release -rd
Description:Ubuntu 12.10
Release:12.10
apt-cache grub2-common
E: Invalid operation grub2-common
root@kvm-03f:/mnt/tmp/boot/grub# apt-cache policy grub2-common
grub2-common:
Installed: 2.00-7ubuntu11
Candidate: 2.00-7ubuntu11
Version table:
*** 2.00-7ubuntu11 0
Please see the attached results.
Two more comments:
In a re-test I commanded Ubuntu installer to also install grub into the MBR on
/dev/sdc, but bootinfo detects none. I also had no result trying to boot from
that disk.
I've copied grub.cfg from the latest installation to the older
Hi,
I've tested this in quantal, and everything works OK.
The pci device is present with every restart of the client, including
the connected usb device. All devices are working properly, including
removing and adding the usb divice.
Thanks for pointing me to quantal, I will test some different
Hi,
I've tested this in quantal, and everything works OK.
The pci device is present with every restart of the client, including
the connected usb device. All devices are working properly, including
removing and adding the usb divice.
Thanks for pointing me to quantal, I will test some different
Public bug reported:
A restarted kvm client with a passthough pci device does not work
anymore (properly) with that device. The device does not seem to be re-
set properly.
If the KVM host is re-started the client one time starts properly with a
correctly functioning pci device, when the client
$ lsb_release -rd
Description:Ubuntu 12.04.1 LTS
Release:12.04
$ apt-cache policy qemu-kvm
qemu-kvm:
Installed: 1.0+noroms-0ubuntu14.2
Candidate: 1.0+noroms-0ubuntu14.3
Version table:
1.0+noroms-0ubuntu14.3 0
500 http://nl.archive.ubuntu.com/ubuntu/
Fresh start:
@pci-02:~$ lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
(On the
Public bug reported:
A restarted kvm client with a passthough pci device does not work
anymore (properly) with that device. The device does not seem to be re-
set properly.
If the KVM host is re-started the client one time starts properly with a
correctly functioning pci device, when the client
$ lsb_release -rd
Description:Ubuntu 12.04.1 LTS
Release:12.04
$ apt-cache policy qemu-kvm
qemu-kvm:
Installed: 1.0+noroms-0ubuntu14.2
Candidate: 1.0+noroms-0ubuntu14.3
Version table:
1.0+noroms-0ubuntu14.3 0
500 http://nl.archive.ubuntu.com/ubuntu/
Fresh start:
@pci-02:~$ lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600
(On the
Public bug reported:
When accessing a Windows based webserver from work where my work (Active
Directory) credentials are required Firefox becomes largely
unresponsive. It does seem to process the website, but it isn't usable
anymore and the firefox windows greys out for most of the time. It even
I'm seeing this exact behaviour on my laptop. I run the Xorg-edgers PPA
since a couple of months that PPA also provides the LTS-backport kernel
(quantal? kernel) so, that kernel is quite recent (3.5.x with
backports). If needed I can run the latest 3.6-rc from the mainline
kernel PPA.
Do you
Hi,
Performed the test in quantal-server-amd64.iso and this is no issue in
Quantal. The LoadFile directive looks nice without any absolute path,
probably using some LD_LIBPATH or LIBRARY_PATH in the background.
root@b64s1210:/etc/apache2/mods-enabled# dpkg -l | grep proxy-ht
ii
Hi,
ran the sed command and apache starts with the module enabled (both 64 and 32
bit installations).
This issue seems to be resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005425
Title:
IMPACT:
LOW-MEDIUM
Site-forwarding is not possible,
- 12.04 cannot be used as a forwarding host to link to sites hosted within a
private network.
(just keep using previous ubuntu version for the moment)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Please see [Bug 1005425] for further details, I've had a problem using
proxy_html, but did see mod-security uses the same wrong LoadFile
directive.
Actions should be repeated for mod-security.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libapache-mod-security (not
Public bug reported:
Hi,
The following packages produce a coredump when (re)installing.
libapache2-mod-parser3
libapache2-mod-rivet
libapache2-mod-rpaf
They are corecumping when apache is started and modules are enabled, but the
install process is not completed and are handled with
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1006724
Title:
coredump while apt installing packages
To manage notifications about this bug go to:
Hi,
The command to use is
uname -i
This produced your excepted strings on the different platforms.
I've quickly looked at other apache modules, and mod_serurity also has
the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
See also package libapache2-mod-proxy-html , file/link /etc/apache2
/mods-enabled/proxy_html.load
# lsb_release -rd
Description:Ubuntu 12.04 LTS
Release:12.04
(64 bit)
# apt-cache policy libxml2
libxml2:
Installed: 2.7.8.dfsg-5.1ubuntu4.1
Candidate:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005425
Title:
Library not found where extected (by libapache2-mod-proxy-html)
To manage notifications about this bug go to:
I've noticed this on a 64 bit installation, but 32 bit also lacks these
files under /usr/lib
(from 32 bit:
$ dpkg -L libxml2
/.
/usr
/usr/lib
/usr/lib/i386-linux-gnu
/usr/lib/i386-linux-gnu/libxml2.so.2.7.8
/usr/share
/usr/share/doc
/usr/share/doc/libxml2
/usr/share/doc/libxml2/AUTHORS
Hi,
geus@b32s1204:~$ uname -m
i686
(image ubuntu-12.04-server-i386.iso used to install inside kvm hypervisor)
Gerben
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1005425
Title:
[SRU] Not looking
Public bug reported:
issuing the halt commando (e.g. halt as root) will not switch off the
computer. All services will be stopped, a final ¨ * Will now haltis
posted on the console (a desktop installation), but the computer does
not switch off. Either it needs to be switched off at the machine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/975867
Title:
/sbin/halt fails to halt system
To manage notifications about this bug go to:
The graphical output at the console (pressing 'esc' when shutting down).
Last lines read:
* Will now halt
[ 38.922882] System halted.
** Attachment added: ubuntu_11.10_dskt_64_halt_hangs_2.png
This is what I did (with gnome 12.04 in the latest virtualbox, and i had
not used 12.04 for about a week):
* boot into gnome unity
* decided to install gnome-panel, using the software center
* log out and log in again with gnome-panel (gnome classic), which worked fine
* installed all available
1 - 100 of 149 matches
Mail list logo
