+1 for revisiting this issue for intrepid.
--
New upstream release 3.1.0.0
https://bugs.launchpad.net/bugs/128525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubu
Sorry for the double post. This time really with the files.
--
Black screen during install after configuring of xserver (on certain intel
graphics cards)
https://launchpad.net/bugs/41106
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-b
Attached are the relevant configuration files.
If there is anything more you need, let me know.
At what time (UTC) will the 20060824 version of edgy be posted?
Thanks for taking care of the bug.
--
Black screen during install after configuring of xserver (on certain intel
graphics cards)
http
Just tried edgy alternate cd of the 29.2 of august, and it did not work
on my laptop (with Intel graphic card), though it works fine on another
machine (not with an Intel graphic card).
--
Black screen during install after configuring of xserver (on certain intel
graphics cards)
https://launchpa
I have the same problem on my Dell Inspiron 510m Notebook with the
current edgy kubuntu version. This bug also occurs when restarting from
hibernate mode.
--
Mouse cursor disappears after suspend
https://launchpad.net/bugs/64333
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://l
Well not that I would really know, but wouldn't it be much better to
detect the system during installation and only use a modified version of
the khotkeysrc if the system is one where the keycode 204 is supposed to
open the CD-drive.
Unless of course this is some kind of standardized keycode for o
After having upgraded from Kubuntu Feisty Fawn to the Gutsy beta Release and a
few upgrades down the road, I had a very similar issue, and commenting out
(i.e. adding a # to the start of the line) the lines starting with iface in my
/etc/network/interfaces, seems to have solved it for me.
I th
Thanks for your efforts.
I have attached my khotkeysrc to give you an idea what mine looks like.
I have also tested your khotkeysrc and it works for me :-).
If you need anything else, let me know.
** Attachment added: "old khotkeysrc"
http://launchpadlibrarian.net/9706704/khotkeysrc
--
The
I am observing the same effect on a 32bit Feisty system (firefox plugin
version: 0.8.0~cvs20070611.1016-1ubuntu3~feisty1)
--
Youtube videos have horizontal white lines
https://bugs.launchpad.net/bugs/129019
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I just did sudo aptitude update && sudo aptitude dist-upgrade and the
2.6.20-15-386 kernel was downloaded. It booted fine so it seems to me
the bug could be set to fixed.
uname --all
Linux ubuntu 2.6.20-15-386 #2 Sat Apr 14 00:50:49 UTC 2007 i686
GNU/Linux
--
MASTER: Computer will not boot afte
I attached the output of lshal -l for further information about my
hardware.
** Attachment added: "lshal.txt"
http://librarian.launchpad.net/7873949/lshal.txt
--
(k)ubuntu 7.04 does not recognize a partition (only the harddrive) that was
recognized in edgy
https://bugs.launchpad.net/bugs/11
Public bug reported:
Binary package hint: hal
I have 3 IDE hard disks, which used to work in Edgy without a glitch.
Now the partition of the drive that is hanging on the second IDE bus as
slave is no longer recognized (master is DVD-Burner). Note that the
drive itself is still recognized, i.e. I
This seems to be fixed in Gnome but unfortunately not in KDE
(respectively kubuntu).
I don't know if it helps, but this is my xev output for this key:
KeyRelease event, serial 28, synthetic NO, window 0x3c1,
root 0x4d, subw 0x0, time 21003931, (725,532), root:(728,556),
state 0x0, ke
Public bug reported:
Binary package hint: hotkey-setup
On a Dell Inspiron 510m the hotkey (Fn+F10) that should eject the DVD-drive
does not work in KDE.
Though it does work in Gnome. (As documented in Bug #33778)
I don't know if it helps, but this is my xev output for this key:
KeyRelease even
After updating to Feisty "rm -r ~/.azureus/logs" fixed the problem for
me too, i.e. it starts up and I have no crashes since then. By the way
is there still a chance of an upgrade to 2.5.0.4 for feisty?
--
Azureus does not start
https://bugs.launchpad.net/bugs/57875
You received this bug notifica
I tried using a chroot environment, as described here:
https://wiki.kubuntu.org/KubuntuDistUpgrade
Unfortunately the DistUpgrader crashed on me.
I have attached
/var/log/dist-upgrade/apt.log
/var/log/dist-upgrade/main.log
and the traceback that the GUI showed when it told me that the
DistUpgra
*** This bug is a duplicate of bug 63258 ***
** This bug has been marked a duplicate of bug 63258
Mouse cursor goes invisible after return from suspend
--
Mouse cursor gone after hibernate/resume
https://launchpad.net/bugs/64428
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https
*** This bug is a duplicate of bug 63258 ***
** This bug has been marked a duplicate of bug 63258
Mouse cursor goes invisible after return from suspend
--
Mouse cursor disappears after suspend
https://launchpad.net/bugs/64333
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
This bug did not occur with firefox 1.99+2.0b2+dfsg-1ubuntu2 on a edgy kubuntu
system.
But I had to uninstall flashplugin first, i.e. with the flashplugin firefox did
crash.
(note: just deleting the $HOME/.mozilla directory did NOT do the job I had to
actually write to a command line:
sudo
Public bug reported:
On my Asus X93SV-YZ225V laptop my mouse as well as all other 'human interface
devices' (I tried it with a second mouse and a keyboard) stop working at a
random time after boot, when attached to a USB 2.0 port.
Other USB-devices (I tried it with several USB Flash drives) cont
Just checked.
The upstream Kernel versions: 4.1.0-040100rc7-generic #201506080035 and
3.19.8-031908-generic #201505110938 from
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D don't seem to exhibit
this problem.
Will try to do a git bisect between "355957e Linux 3.19.8" and "a52caa6 UBUNT
** Package changed: xorg (Ubuntu) => linux-lts-vivid (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464723
Title:
Human interface devices stop working on USB 2.0 ports after some time,
co
I finished the git bisect between "355957e Linux 3.19.8" and "a52caa6 UBUNTU:
Ubuntu-3.19.0-20.20".
The first bad commit seems to be 171cf878ea3fed6722e49d3d7da2588967008526.
I just subscribed the responsible committer.
Will now try master-next (
7c1f75fcd0efb22069a5a935d3d042392f308100) with an
I have to correct my previous statements. I retested the kernel releases
I previously thought of as good and I am now observing the bug there as
well.
So I currently don't have a known good version of the kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1464723
Title:
Human interface devices stop working on USB 2.0 ports after some time,
continue to work on US
I just tested the linked upstream kernel. It does not change the
behavior, I am observing the same bug on v4.1-rc8-unstable.
I added the tag accordingly.
Regarding the question whether this was happening after an upgrade.
Well it's actually a little complicated.
If my memory does not deceive me,
** Changed in: dosbox (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997325
Title:
dosbox and timidity daemon don't play nice
To manage notifications abo
I have changed the status from expired back to confirmed because kubuntu
14.10 still shows this bug.
Also as far as I can tell the commit mentioned in comment #3
(https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/997325/comments/3)
is not responsible for this behavior.
Unless there are some w
Just to confirm that commit[r3370] is not the culprit here, I reverted that
commit in the latest svn version of dosbox, and as expected, it only changes
whether the midi ports have to be manually configured or not.
The buggy behavior described here is completely unchanged.
--
You received this
This does not seem to be a dosbox problem, but rather a remnant of the problems
introduced by the introduction of pulseaudio.
Since pulseaudio is not run as a system service by default (cf.
/etc/init/pulseaudio.conf) timidity probably shoud not either.
This entry in the Arch wiki seems to descri
30 matches
Mail list logo
