[Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
** 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 USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
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, I did not observe this problem when I installed Ubuntu 12.04 on this laptop in 2012. Some time afterwards, after an update this problem occurred. Unfortunately at the time I was otherwise occupied so I just attached the mouse to the USB 3.0 port and did not report the bug. And by the time my schedule had cleared up a bit I had forgotten all about the problem, until I recently switched USB ports with the mouse and stumbled upon it again. So it is probably a regression albeit only compared to a three year old kernel. I will try testing the 12.04.X releases and see if I can actually find a reliably good version, and then maybe start bisecting from there, though this may take some time. If some other debugging information would be useful let me know. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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 USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
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, 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 USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
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 and without the 171cf87 commit reverted. Some input regarding further useful tests or regarding further code changes would be appreciated. ** Attachment added: Log of mentioned git bisect https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1464723/+attachment/4414674/+files/git_bisect_log_1.1.txt -- 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 USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
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 UBUNTU: Ubuntu-3.19.0-20.20 and see what that turns up. -- 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 USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464723] Re: Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
** 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, continue to work on USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1464723] [NEW] Human interface devices stop working on USB 2.0 ports after some time, continue to work on USB 3.0
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) continue to work on the USB 2.0 ports. The USB 3.0 port on the laptop does not show this behavior, i.e. a human interface device never stops working. Unplugging and replugging the mouse does not reactivate it. The mouse works again for a random amount of time after a reboot or a wake-up from suspend to RAM. When the mouse stops working the respective /dev/input/mouseX device does not produce any output either. The touchpad, that is connected via PS/2, does not show this bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jun 12 14:50:29 2015 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:105c] InstallationDate: Installed on 2015-05-16 (26 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422) MachineType: ASUSTeK Computer Inc. K93SV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-20-generic root=UUID=4f453054-6eeb-4f48-ba87-b529b2fcd617 ro nosplash SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/22/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K93SV 209 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K93SV dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK93SV209:bd11/22/2011:svnASUSTeKComputerInc.:pnK93SV:pvr1.0:rvnASUSTeKComputerInc.:rnK93SV:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K93SV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Fri Jun 12 13:08:49 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6152 vendor CMO xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid ** Attachment added: recommended attachments according to https://wiki.ubuntu.com/DebuggingMouseDetection; https://bugs.launchpad.net/bugs/1464723/+attachment/4413990/+files/test.zip -- 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 USB 3.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1464723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997325] Re: dosbox and timidity daemon don't play nice
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 describe the same issue: https://wiki.archlinux.org/index.php/timidity#Daemon It might be better to just autostart something like /usr/bin/timidity -Os -iAD when the user logs in, instead of starting a system wide daemon at boot time. But maybe someone with a deeper knowledge of how the ubuntu audio stack is supposed to work could weigh in on this. ** Package changed: dosbox (Ubuntu) = timidity (Ubuntu) ** Changed in: timidity (Ubuntu) Status: Incomplete = 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/timidity/+bug/997325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997325] Re: dosbox and timidity daemon don't play nice
** 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/997325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997325] Re: dosbox and timidity daemon don't play nice
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 weird side effects, the commit[r3370] just prevents dosbox from using timidity in its default configuration, but does not stop the user from explicitly specifying it in the configuration file 'dosbox.conf'. -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/997325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997325] Re: dosbox and timidity daemon don't play nice
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 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dosbox/+bug/997325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 128525] Re: New upstream release 3.1.0.0
+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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 149869] Re: Gutsy Beta Kubuntu could not connect
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 think this is more or less the upgrading issue mentioned on http://www.ubuntu.com/getubuntu/releasenotes/710 under Network Manager. Michael -- Gutsy Beta Kubuntu could not connect https://bugs.launchpad.net/bugs/149869 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111943] Re: The eject button does not work on Dell Inspiron 510m in KDE
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 eject button does not work on Dell Inspiron 510m in KDE https://bugs.launchpad.net/bugs/111943 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 111943] Re: The eject button does not work on Dell Inspiron 510m in KDE
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 opening CD-drive the same keycode could be used for different things on different keyboards. I guess all I am trying to say is if your Khotkeysrc is put by default on every computer running kubuntu it could break special keys on other keyboards by fixing the bug for me. On that note /usr/share/hotkey-setup/dell.hk seems to be a table actually describing dell specific keys and it lists Fn+F10 as $KEY_EJECTCD ** Attachment added: dell.hk http://launchpadlibrarian.net/9711751/dell.hk -- The eject button does not work on Dell Inspiron 510m in KDE https://bugs.launchpad.net/bugs/111943 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 129019] Re: Youtube videos have horizontal white lines
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 bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117686] Re: (k)ubuntu 7.04 does not recognize a partition (only the harddrive) that was recognized in edgy
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/117686 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 117686] (k)ubuntu 7.04 does not recognize a partition (only the harddrive) that was recognized in edgy
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 have a /dev/sdc but not a /dev/sdc1. The drive also works with the Feisty life CD but not with the install. ** Affects: hal (Ubuntu) Importance: Undecided Status: Unconfirmed -- (k)ubuntu 7.04 does not recognize a partition (only the harddrive) that was recognized in edgy https://bugs.launchpad.net/bugs/117686 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 33778] Re: The eject button does not work on Dell Inspiron 510m
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, keycode 204 (keysym 0x1008ff2c, XF86Eject), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False -- The eject button does not work on Dell Inspiron 510m https://bugs.launchpad.net/bugs/33778 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 111943] The eject button does not work on Dell Inspiron 510m in KDE
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 event, serial 28, synthetic NO, window 0x3c1, root 0x4d, subw 0x0, time 21003931, (725,532), root:(728,556), state 0x0, keycode 204 (keysym 0x1008ff2c, XF86Eject), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ** Affects: hotkey-setup (Ubuntu) Importance: Undecided Status: Unconfirmed -- The eject button does not work on Dell Inspiron 510m in KDE https://bugs.launchpad.net/bugs/111943 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 106063] Re: MASTER: Computer will not boot after 2.6.20-14.23 kernel upgrade
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 after 2.6.20-14.23 kernel upgrade https://bugs.launchpad.net/bugs/106063 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [EMAIL PROTECTED] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57875] Re: Azureus does not start
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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84717] Re: SRU: updates necessary for Kubuntu Upgrade Tool in Edgy
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 DistUpgrader had crashed. ** Attachment added: /var/log/dist-upgrade/apt.log /var/log/dist-upgrade/main.log traceback http://librarian.launchpad.net/6917290/logs.tar.gz -- SRU: updates necessary for Kubuntu Upgrade Tool in Edgy https://launchpad.net/bugs/84717 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64428] Re: Mouse cursor gone after hibernate/resume
*** 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64333] Re: Mouse cursor disappears after suspend
*** 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 64333] Re: Mouse cursor disappears after suspend
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56911] Re: Firefox Crash
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 aptitude remove flashplugin-nonfree) So maybe the others could check if the problem still exists in the latest firefox releases. -- Firefox Crash https://launchpad.net/bugs/56911 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41106] Re: Black screen during install after configuring of xserver (on certain intel graphics cards)
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://launchpad.net/bugs/41106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 41106] Re: Black screen during install after configuring of xserver (on certain intel graphics cards)
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-bugs
[Bug 41106] Re: Black screen during install after configuring of xserver (on certain intel graphics cards)
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) https://launchpad.net/bugs/41106 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
