It is/was probably just a transitional problem: After using the system
for some time now, I experience no problem. It boots as reliable as
before after it had to re-run the lilo-configuration again, anyhow,
because of me phasing out old(er) kernels. Thanks!
--
You received this bug notification
Public bug reported:
Problem occurred during a (longer) system update
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.9
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
NonfreeKernelModules: zfs
Public bug reported:
Just an upgrade from 16.04.5 to 18.04(.1)
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.1
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon
Public bug reported:
While upgrading from 16.04.5 to 18.04(.1)
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-headers-4.15.0-32-generic 4.15.0-32.35
ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-45-generic x86_64
NonfreeKernelModules: zfs
Public bug reported:
When switching kernels from 4.13.0-45-generic to 4.15.0-24-generic, dkms
fails in buildign the nvidia-340 module(s). My graphics component
doesn't allow for a newer nvidia driver than the 340 one.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340
Public bug reported:
Known error, but for a different Ubuntu (16.04(.2)) and kernel (4.13)
version!
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tp-smapi-dkms 0.41-1
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
You seem to be correct, bug #1539348 describes exactly what happens to
the IDs. I haven't yet checked for the "udevadm info" of the device
(only), just for the whole tree. In the latter case, it is ok, but this
is also the case for bug #1539348!
What bug #1539348 doesn't touch nor resolves is the
I can now confirm my analysis of the bug! And I got a new and
unpleaseant surprise, too.
First I compiled a version of modemmanager (1.4.10) where the wrongly
returned pci-id 8068:3b34 is swapped to the correct usb-id 12d1:14c9 in
"get_device_ids". This is just a hack, of course, no solution. Now
Public bug reported:
Starting with Ubuntu 15.10 (wily) my USB webstick does not work any
longer. It used to work with Ubuntu for several previous versions.
My stick is a Huawei E173s-1 with a usb-vendor/-product id 12d1:14d1 before and
12d1:14c9 after 'modeswitch'.
The - or at least one -
Hello!
Regarding the (complete) failure of the mic-key-test with the last
kernel tested (v3.11.10.6-saucy), I can tell you that the situation
has not deteriorated with the 14.04 Ubuntu-live beta version kernel;
but it didn't get better with it, either.
When started from a stick, the mic-key
Hello!
On Mar 12, Joseph Salisbury wrote:
Can you see if this issue also happens with the latest upstream 3.11
kernel?
yes, sorry, it still happens today (Mar 13, 2014), and worse, now it
seems to ignore the MicMute-Key completely, meaning that the LED also
isn't (properly) operated any
Public bug reported:
Starting with linux-kernel 3.11.0-17 (linux-image-
extra-3.11.0-17-generic), on a Lenovo ThinkPad W510 the LED within the
MicMute key is working in the way that it is on by default (meaning mic
is 'mute'/off). It turns off when activating the microphone via
Public bug reported:
Just an update error that crept up. I hope I can deal with it. So this is just
for (your) information. Otherwise I'll post a follow-up.
Thanks.
ProblemType: Package
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-30-generic 3.8.0-30.44
ProcVersionSignature: Ubuntu
Public bug reported:
Dear package-management,
I would like to get a Huawei USB-UMTS-stick to work now and persistently
in future releases and avoid a kernel stop/crash at the same time.
My stick is a ProSieben (delivery company), Vodafone (UMTS-, IP-
provider, websession-connection) from
Hello Brian,
I did test your patch in a i386 environment with version
0.9.13-0ubuntu12.1 of libvirt0, libvirt-bin, libvirt-dev, libvirt-doc,
and python-libvirt - it ran fine! Thank you very much! [I didn't install
'libvirt0-dbg'.]
Thanks for the quick reaction-time, too!
Best wishes.
--
You
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1074418
Title:
qemu:///sessions fail, when libvirtd hasn't been started properly
Public bug reported:
Starting with 12.10 the libvirt communications mechanism uses the
XDG_RUNTIME_DIR environment variable to determine the directory to put
in its pipe(s) and controlling files - this normally being
/run/usr/$USER.
Now when you run a qemu user(!) session (qemu:///session) an a
** Description changed:
Starting with 12.10 the libvirt communications mechanism uses the
XDG_RUNTIME_DIR environment variable to determine the directory to put
in its pipe(s) and controlling files - this normally being
- /run/usr/$USER.
+ /run/user/$USER/libvirt.
- Now when you run a
Public bug reported:
Two step upgrade from 11.04 to 11.10 (fine as far as gxine is concerned)
and then 11.10 to 12.04, which triggered the error. The update was done
by 'update-manager' each time.
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: gxine 0.5.905-4ubuntu6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992034
Title:
package gxine 0.5.905-4ubuntu6 failed to install/upgrade:
ErrorMessage: subprocess installed post-installation script returned
error
Public bug reported:
Binary package hint: xine-ui
Just a normal 'dist-upgrade' (10.10 - 11.04), nothing fancy. Somehow
xine-ui didn't like it :-).
ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop]
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/788632
Title:
package xine-ui 0.99.6-1 [modified: var/lib/xine/xine.desktop] failed
to install/upgrade: ErrorMessage: subprocess installed post-
Hello,
On Nov 27, Evan Broder wrote:
Thanks for the great bug report. Your description of the problem made it
really simple to track down the misbehavior.
you're welcome and ...
[Description of possible solution.]
.. your patch/fix seems to work!
I've pushed a patch to
Public bug reported:
Binary package hint: initramfs-tools
Hello!
There's a long startup delay (until 'rootdelay' has passwd), when a
(root-)device is set up in the /dev-tree only.
This is (e.g.) the case, when the machine is started by 'lilo' and the
root-device given as device numbers like
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/47935176/Dependencies.txt
--
wait-for-root has problems with mknod generated root-devices
https://bugs.launchpad.net/bugs/576429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Comming back to the 'merged' bug #470797: Can't you just 'mimic' the
Sys-V-init behaviour in upstart. That seemed to work satisfactorily.
Package 'initscripts' installed a shell-script mountall-bootclean.sh
which started some helper (also a shell-script, iirc) that did the
actual job. It's all
SInce you asked for it, here is my /etc/fstab. Fairly common I'd guess.
The only thing is that I'm dedicating a harddisk partition to /tmp.
** Attachment added: /etc/fstab with /tmp as a separate partition
http://launchpadlibrarian.net/35469662/fstab
--
/tmp isn't cleaned up on boot/startup
Public bug reported:
Binary package hint: sysvinit
After upgrading from 9.04 (jaunty) to 9.10 (karmic), /tmp isn't cleaned
up any longer when booting.
This used to be done with a script mountall-bootclean.sh and its helpers
coming from package 'initscripts'. Now it is missing there, but it also
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34955411/Dependencies.txt
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/34955412/XsessionErrors.txt
--
/tmp isn't cleaned up on boot/startup any longer
https://bugs.launchpad.net/bugs/470797
You
Public bug reported:
I'm not sure that it is a probelm of rhythmbox and would assume it isn't. It is
a problem of upgrading an intrepid system on proposed status today (Jan 30,
2009) with a lot of programs, specially (lib-)xine ones, gxine and some libgtk2.
It threw an dpkg:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/21800285/Dependencies.txt
** Attachment added: DpkgTerminalLog.txt
http://launchpadlibrarian.net/21800286/DpkgTerminalLog.txt
--
package rhythmbox 0.11.6svn20081008-0ubuntu4.3 failed to install/upgrade:
package
On Dec 01, Chris Coulson wrote:
Hang on, I'm wrong! I shouldn't have just skimmed through your post
before replying ;)
I did hang on :-).
Ok, so what you're saying is that the stop action failed during the
upgrade because the daemon had failed to start earlier for some other
reason. Missing
think you might have to help other
people with the same problem.
Thanks for caring and for the fine software,
Ruediger Oberhage
--
Dr. H.-R. Oberhage
Mail: Univ. Duisburg-Essen E-Mail: [EMAIL PROTECTED]
Fachbereich Physik[EMAIL PROTECTED]
Campus Duisburg, MG 464
I'd like to add to my remarks dated 2007-10-23, that I've now found the
config file for 'totem' alias Movie Player under gnome. Activating the
'video.driver' entry and setting it to xshm in
~/.gnome2/Totem/xine_config now allows me to use totem like it used to
be in version 7.04 alias feisty - and
I'd like to an observation and a (maybe) workaround for some.
The observation is, that for me, before calling totem for the first time, runs
without an error, but (already) returns no values for the attribute starting
with XV_BLENDING_MODE in the 'client gettable attribute' entry. After
Sorry about too many typos in my above posting. To make it more
understandable:
I'd like to add an observation ...
It should read: ... first time, xvinfo runs without an error ...
and: ...xvinfo now fails, too, exactly at ...
--
xine and totem-xine crashes with the fglrx driver
36 matches
Mail list logo
