[Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
@Sebastian Bacher - genuine question: does not a single person in the chromium-snap team use this feature? Because I can't think of any other reason why this regression (when compared to regular chromium) is treated like a 'wishlist' item. Please, enlighten me. Currently, on any Ubuntu recent Ubuntu version you're forced to use privacy-invading Chrome if you want to use WebApps. Firefox removed the feature (curiously enough, it does work on mobile), chromium-snap crippled it, chromium non-snap is pretty hard to install for most users and leaves you with a(nother) third-party repo on your system. So what's the rationale here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
Such a shame users are being pushed towards regular Chrome, since that's the only feasible 'solution' to this bug for most users. Personally, I've completely given up on Chromium for Ubuntu 20.04+. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313784] Re: File descriptors leaked on lvs invocation
Glad I found this bugreport. The message got me worried, and I can imagine it will keep on creating the same thought with many more people until it (finally!) gets suppressed. Just got this on 20.04 today while running apt autoremove: Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-54-generic Found initrd image: /boot/initrd.img-5.4.0-54-generic Found linux image: /boot/vmlinuz-5.4.0-53-generic Found initrd image: /boot/initrd.img-5.4.0-53-generic File descriptor 10 (/var/lib/dpkg/triggers/linux-update-5.4.0-48-generic (deleted)) leaked on lvs invocation. Parent PID 55702: /bin/sh done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313784 Title: File descriptors leaked on lvs invocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1313784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870431] Re: Ubuntu booting takes a long time when secure boot is enabled
What I'm noticing on 20.04 is that since the (fresh) installation and enabling of secureboot, it takes well over 30 seconds before the LENOVO logo is shown on my laptop. Before that, it's just black. Any key I press during that time results in the black screen remaining indefinitely. Once the logo appears, booting is pretty fast. I have not experienced (or perhaps noticed, since the screen remains black for such a long time) that the system is booting twice on every reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870431 Title: Ubuntu booting takes a long time when secure boot is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1870431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732482] Re: [snap] doesn't properly save desktop files for "create shortcuts" action
As per the views on https://askubuntu.com/questions/1233058/chromium- snap-on-ubuntu-20-04-some-webapp-shortcuts-not-working- workaround/1233059#1233059, this bug affects many more people than indicated here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732482 Title: [snap] doesn't properly save desktop files for "create shortcuts" action To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93)
Pretty curious why this bug isn't mentioned on https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Desktop ? Since this is a real show stopper for anyone using Ubuntu Desktop seriously AND the issue was reported months before the release of 20.04, it should at the very least have been clearly communicated via i.e. the release notes mentioned above. Where can I file bugs so the process is improved an users will never (unknowingly) run into issues such as these again? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) with LibreOffice is broken in Ubuntu 19.10 & 20.04 (see comment 93) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878723] Re: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update
So if I'm on 20.04, not running Upstart and not experiencing kernel panics, why would I want to install this 'update', re-introducing known security issues? Why is it even pushed to systems running 20.04 without Upstart? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878723 Title: Kernel panic when used with upstart after 0.11-4ubuntu2.1 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1878723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020745] Re: Update to 2.5.3
More than 9 years later, history is repeating itself. 2.9.3 should be backported to 18.04, providing a fix for the broken MusicBrainz support in the default 2.8 series. ** Changed in: abcde (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/1020745 Title: Update to 2.5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abcde/+bug/1020745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 406840] Re: abcde fails to connect to CDDB
Fixed in the 2.9.x series at the very least. ** Changed in: abcde (Ubuntu) Status: Confirmed => 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/406840 Title: abcde fails to connect to CDDB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abcde/+bug/406840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846957] Re: MusicBrainz support deprecated on 2.8.1 -> please backport 2.9.x
I can confirm that 2.9.3 from Disco archives works fine as well on 18.04 (after satisfying dependencies), restoring MusicBrainz functionality. Please, backport! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846957 Title: MusicBrainz support deprecated on 2.8.1 -> please backport 2.9.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abcde/+bug/1846957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846957] Re: MusicBrainz support deprecated on 2.8.1 -> please backport 2.9.x
Just manually download abcde 2.9.2 from Cosmic archives, needed libwebservice-musicbrainz-perl_1.0.4-2_all.deb from the same repo. After satisfying dependencies, both installed fine and now MusicBrainz works flawlessly again. IMHO, the packages can be safely (and easily) backported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846957 Title: MusicBrainz support deprecated on 2.8.1 -> please backport 2.9.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abcde/+bug/1846957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846957] [NEW] MusicBrainz support deprecated on 2.8.1 -> please backport 2.9.x
Public bug reported: The version of abcde (2.8.1, released in January 2017) shipping with Ubuntu 18.04 LTS has deprecated support for (at least, but probably not limited to) MusicBrainz. This makes the application essentially unusable as the metadata of every CD has to be typed in manually. Please provide backports of the 2.9.x version (available on 18.10 and 19.04) which should have fixed this issue. Sources: https://blog.metabrainz.org/2018/02/01/web-service-ver-1-0-ws-1-will-be-removed-in-6-months/ https://abcde.einval.com/download/ ** Affects: abcde (Ubuntu) Importance: Undecided Status: New ** Description changed: The version of abcde (2.8.1, released in January 2017) shipping with Ubuntu 18.04 LTS has deprecated support for (at least, but probably not - limited to) MusicBrains. + limited to) MusicBrainz. This makes the application essentially unusable as the metadata of every CD has to be typed in manually. Please provide backports of the 2.9.x version (available on 18.10 and 19.04) which should have fixed this issue. Sources: https://blog.metabrainz.org/2018/02/01/web-service-ver-1-0-ws-1-will-be-removed-in-6-months/ https://abcde.einval.com/download/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846957 Title: MusicBrainz support deprecated on 2.8.1 -> please backport 2.9.x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/abcde/+bug/1846957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637878] Re: Network Manager does not show VLANs
@Brandon / #15 - indeed I can check "Show virtual connections" (the 'and configure'-part seems to be missing), but after that there's still no sign of any VPN settings in the System Settings Module. Perhaps I'm missing something? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637878 Title: Network Manager does not show VLANs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-nm/+bug/1637878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825506] Re: Uses deprecated AVStream.codec to pass codec parameters to muxers
** Also affects: gscan2pdf Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825506 Title: Uses deprecated AVStream.codec to pass codec parameters to muxers To manage notifications about this bug go to: https://bugs.launchpad.net/gscan2pdf/+bug/1825506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825506] [NEW] Uses deprecated AVStream.codec to pass codec parameters to muxers
Public bug reported: When using a scanning tool like gscan2pdf (which uses unpaper 6.1 to clean up scans) on Ubuntu 18.04, I get the following error: "Error running unpaper: [image2 @ 0x551234567890] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead. [image2 @ 0x551234567890] Encoder did not produce proper pts, making some up." According to the gscan2pdf author, this is a bug in unpaper: https://sourceforge.net/p/gscan2pdf/support-requests/34/ ** Affects: unpaper (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825506 Title: Uses deprecated AVStream.codec to pass codec parameters to muxers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unpaper/+bug/1825506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’]
I'm done with this. Took out the nVidia card today, only to run into the same old performance problems (i.e. no smooth video playback) with the i915 driver (which were the initial reasons to switch to nVidia). Even without the card, I'm still running into this bug. Guess I have to manually remove the nVidia drivers as well. What a mess. AMD here I come. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’]
I ran into this bug *again* with today's updates and STILL need to boot the 4.13 kernel to get into my system. Could someone *pretty please* apply the patches Max proposed? 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/1737750 Title: nvidia-graphics-drivers fail to build [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
And again with today's updates. 8 months and still no fix. What a mess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
I was hoping this would have been fixed with today's updates, as the xorg update mentioned something in the terms of 'prevent nvidia regression'. But alas, still need to manually boot kernel 4.13 to get beyond lightdm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737750] Re: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’]
So even while this bug has been known to exist for more than half a year, it still managed to slip into the automatic updates of an LTS (16.04) release: https://bugs.launchpad.net/bugs/1779687 Ouch. I hope this doesn't mean systems with older nVidia cards are just out of luck? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737750 Title: nvidia-graphics-drivers-304 304.137-0ubuntu2 ADT test failure with linux 4.15.0-1.2 [error: implicit declaration of function ‘init_timer’] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1737750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779687] Re: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to build
I just bumped into bug during a regular (automatic) system update. Apparently, we're auto-upgrading from kernel 4.13 to 4.15? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779687 Title: nvidia-340 340.104-0ubuntu0.16.04.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1779687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572321] Re: owncloud network access is disabled
@slash (slash-tux): IMHO you'd be better of to switch to Nextcloud, even though they don't seem to provide a native arm build of their client either. I did find a guide to build it from source though (assuming you're using a machine like RPi): https://help.nextcloud.com/t /nextcloud-client-for-raspberry-pi/27989/5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572321 Title: owncloud network access is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/owncloud-client/+bug/1572321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full
Ben, I feel your pain and couldn't agree more. I'm under the impression that this attitude is getting more common as Canonical focuses on server and IoT. Where are the days where the 100 Papercuts (https://wiki.ubuntu.com/One%20Hundred%20Papercuts) got a really high priority? IMHO, this bug sure seems to qualify... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357093 Title: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1573959] Re: On-screen text disappears after suspend
Nils, please upgrade your kernel as per the bug description: WORKAROUND / 'FIX' (added on March 9, 2017) Several people have mentioned upgrading to kernel 4.8 or higher solves the issue. As per #81, you can easily install kernel 4.8 (if you're on Ubuntu 16.04, that is) by running sudo apt install linux-generic-hwe-16.04 If you are still experiencing this issue after upgrading to kernel 4.8, please report back. ** Also affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1573959 Title: On-screen text disappears after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1573959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 344878] Re: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry)
Thanks mhalcrow for your elaborate reply. While appreciated, IMHO you don't need to apologize. It's not your fault we as end-users weren't notified of this limitation during installation. For a lot of us, the situation looks pretty sad. There's eCryptfs which has the file name limitation and there's full disk encryption which is (AFAIK) only available on the alternate installer. And last time I heard, full disk encryption poses problems when Windows is installed on the same disk, leaving eCryptfs as the only option to many of us. So kudos for trying to fix this! About your proposed solution - as an Ubuntu 16.04.2 user with (currently) 4.10 kernel, does this mean I could use ext4 encryption without too much risks or would I still be in "early adopter" territory? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/344878 Title: file name too long when creating new file (ecryptfs_lookup: lookup_one_len() returned [-36] on lower_dentry) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/344878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
What's up with all the spamming on Launchpad lately? Please, ban these accounts. Unsubscribing to all notificiatons on this bug (also since despite it's affecting over 650 people and has a heat value of over 4000, it's not even assigned to anyone...). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ambasa/+bug/349469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 162413] Slightly different error when using a 'freshly' booted machine
I'm also getting this slightly different error when following the steps mentioned above, but with a 'freshly' booted machine: SoftMAC: Open Authentication with 00:0e:a6:63:10:b5 failed, error code: 13 I don't know if this makes any difference, but the problem is just as annoying (having to type this in Windows because I can't connect using Ubuntu). -- Connecting to WEP-encrypted networks using shared key impossible https://bugs.launchpad.net/bugs/162413 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 129982] Re: Default keyboard layout for Dutch language
Confirmed, I'm ashamed I didn't post a bug about this when I first mentioned it (must have been when Hoary came out...). A bad thing to get used to! -- Default keyboard layout for Dutch language https://bugs.launchpad.net/bugs/129982 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 162413] Re: Connecting to WEP-encrypted networks using shared key impossible
I really don't know if this bug is connected to KNetworkManager, since I don't use KDE. Can anyone else confirm this (and my problem)? :) -- Connecting to WEP-encrypted networks using shared key impossible https://bugs.launchpad.net/bugs/162413 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 162413] Connecting to WEP-encrypted networks using shared key impossible
Public bug reported: When connecting to a WEP-encrypted WiFi network, using 'Shared Key' as authentication method, the system uses the 'Open System' authentication method instead. At least, this is my suspicion when I try to connect to such a network and I'm not getting access (while the credentials are okay). Opening a console and typing 'dmesg' produces the following output: [ 1997.197199] SoftMAC: Open Authentication with 00:0e:a6:63:10:b5 failed, error code: 1 [ 1997.558916] SoftMAC: Open Authentication with 00:0e:a6:63:10:b5 failed, error code: 1 This message is repeated several times. When I'm using WinXP on the same machine, connecting to the same network, using the same credentials, the connection is established without any problems. System info: HP Pavilion zv6000 (broadcom bcm43xx) Ubuntu 7.10 ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Connecting to WEP-encrypted networks using shared key impossible https://bugs.launchpad.net/bugs/162413 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 138470] Re: [gutsy tribe 5] installer doesn't work with XFS root filesystem
Fixed in Gutsy final ** Changed in: ubiquity (Ubuntu) Status: New = Fix Released -- [gutsy tribe 5] installer doesn't work with XFS root filesystem https://bugs.launchpad.net/bugs/138470 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 116650] Re: Imation Disc Stakka C10AI goes wild when connected to PC
This bug is still present in Gutsy, so I guess linux-source-2.6.22 is also affected... -- Imation Disc Stakka C10AI goes wild when connected to PC https://bugs.launchpad.net/bugs/116650 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 116662] Reconfirmed on Gutsy Beta
When booting from the Gutsy Beta live CD (both Ubuntu and Kubuntu), the problem is still there. -- screen output is corrupted on Dell OptiPlex GX115 and GX150 https://bugs.launchpad.net/bugs/116662 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 138470] [gutsy tribe 5] installer doesn't work with XFS root filesystem
Public bug reported: When installing Gutsy tribe 5 from the liveCD, reformatting an existing XFS partition and using that as the root filesystem results in the installer not continuing. Steps to reproduce: 1) Boot from Gutsy tribe 5 liveCD, with harddisk already containing an XFS partition and and ext3 /boot partition (this is my situation, I expect the installer to behave the same when creating a new XFS partition or reformatting an existing partition which wasn't XFS before, but I don't know for sure) 2) Start the installation and select the 'manual' partitioning mode 3) Select the existing XFS partition as the root filesystem 4) Tag it to be reformatted 5) Select the ext3 partition as the /boot partition (GRUB can't be installed to an XFS partition directly because of some issue, at least this was the case with Dapper and Edgy - perhaps this is fixed by know) 6) Tag it to be reformatted (installer refuses to continue if you don't, so backup any existing data just in case) 7) Continue the installer Result: installer just 'hangs' for eternity and doesn't continue. It doesn't crash, though - it can be cancelled. I've tried reformatting the root filesystem to ext3 after this during the (restarted) installation process - then the installer continues without a problem. I really want XFS as my root filesystem though, so I consider this a bug. I selected Ubiquity as the package hint, but of course there could be something 'lower-level' causing this problem. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- [gutsy tribe 5] installer doesn't work with XFS root filesystem https://bugs.launchpad.net/bugs/138470 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 138470] Re: [gutsy tribe 5] installer doesn't work with XFS root filesystem
** Description changed: When installing Gutsy tribe 5 from the liveCD, reformatting an existing XFS partition and using that as the root filesystem results in the installer not continuing. Steps to reproduce: 1) Boot from Gutsy tribe 5 liveCD, with harddisk already containing an XFS partition and and ext3 /boot partition (this is my situation, I expect the installer to behave the same when creating a new XFS partition or reformatting an existing partition which wasn't XFS before, but I don't know for sure) 2) Start the installation and select the 'manual' partitioning mode 3) Select the existing XFS partition as the root filesystem 4) Tag it to be reformatted 5) Select the ext3 partition as the /boot partition (GRUB can't be installed to an XFS partition directly because of some issue, at least this was the case with Dapper and Edgy - perhaps this is fixed by know) - 6) Tag it to be reformatted (installer refuses to continue if you don't, so backup any existing data just in case) + 6) Tag it to be reformatted (installer refuses to continue if you don't [is this a bug? Seems to me it is!], so backup any existing data just in case) 7) Continue the installer Result: installer just 'hangs' for eternity and doesn't continue. It doesn't crash, though - it can be cancelled. I've tried reformatting the root filesystem to ext3 after this during the (restarted) installation process - then the installer continues without a problem. I really want XFS as my root filesystem though, so I consider this a bug. I selected Ubiquity as the package hint, but of course there could be something 'lower-level' causing this problem. -- [gutsy tribe 5] installer doesn't work with XFS root filesystem https://bugs.launchpad.net/bugs/138470 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 63090] Re: do not eject all USB/Firewire devices
Sitsofe, If I may quote my comment on bug #36252, https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/36252/comments/40 , perhaps if my suggestion (last part) was implemented, it would solve your problem? [quote] How Kubuntu does it: I ejected (allthough it's called 'safely unmount' in Kubuntu Feisty) an external USB harddrive with an ext3 filesystem. It worked exactly as expected: -The drive spun down and stopped -The icon disappeared from the desktop -The drive was no longer accessible I believe this is how the 'eject' function in Nautilus / gnome-volume-manager should work as well (although I'm not sure how I would want it to behave if I had several partitions on my external drive... probably I would want the system to be smart enough to notice the difference between partitions on a disk and the disk itself. And give two options when I right click on one of those partitions on the desktop: 1) 'Unmount this partition on drive [foo]' and 2) 'Eject entire drive [foo]', followed by a popup, warning the user which partitions will also be unmounted when he/she continues. Or something similar, but this would probably be something for a blueprint? :-) ...). [/quote] In other words, would this be worth a blueprint? -- do not eject all USB/Firewire devices https://bugs.launchpad.net/bugs/63090 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 117170] It's fixed!
Colin, you're my hero! Just changing /dev/wacom to /dev/input/wacom on all three instances in xorg.conf did the trick! If I had ever known my problem was fixable that easy, I would've filed a bug that Ubuntu should just auto-detect and auto-enable this stuff. Heck, I'm gonna change this bug to mention just that. Thanks! -- Wacom pointer not absolute by default https://bugs.launchpad.net/bugs/117170 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 117170] Re: /dev/wacom should be /dev/input/wacom in xorg.conf for USB tablets by default
** Summary changed: - Wacom pointer not absolute by default + /dev/wacom should be /dev/input/wacom in xorg.conf for USB tablets by default ** Description changed: + SOLUTION: The hint Colin gave me below fixed the entire problem + (changing /dev/wacom into /dev/input/wacom in xorg.conf). My question is + - why doesn't Ubuntu detect and change this automatically? It's + something so horribly simple (heck, even the comments in xorg.conf say + so), but because the tablet 'works' by default, I never thought changing + that entry would solve anything. It just kept me looking it all the + wrong directions. + + I changed the Summary of this bug to describe the solution properly. + + *** Original description of the problem: *** + My problem with my Wacom Graphire USB is similar to bug #44279, and has been existing in every Ubuntu release so far where the tablet would work out of the box, including Feisty. Steps to reproduce, partially quoting from bug #44279, adjusted to my situation: 1. Boot any Ubuntu release with Wacom support 2. Plug in the Wacom Graphire tablet (I expect other graphire tablets to exhibit the same problem). 3. Place the Wacom pen in the top left position on the tablet. 4. The mouse pointer should move to the top left corner of the screen. 5. Move the pen diagonally across the tablet towards the lower right corner. Stop when the pen reaches the lower right corner of the tablet. Observe that the mouse pointer has not yet reached the lower right corner of the screen. What you see here is a failed attempt at using absolute positioning. What it looks like is an attempt to translate purely relative positioning into an absolute position much like navigation by dead reckoning. Unfortunately there seems to be a large deviation. This issue is quite annoying for someone working with a tablet, especially since aside from the underrun I describe here, there's also an overrun effect from time to time, where the mouse pointer has already reached the edge of the screen whereas the pen has not yet reached the end of the tablet (main description from bug #44279). There's no telling which one of the two effects will happen when, it seems random and they are both very annoying. One thing this bug does NOT share with bug #44279, is the reference to bug #44274, that seems to be / have been a different problem which I'm not experiencing. Update: I checked the wacom manpage, which mentions this: Option Mode Relative|Absolute sets the mode of the device. I brief 'hurray, found it!' moment flashed my mind. However, when I looked at /var/log/Xorg.0.log I noticed this: (**) stylus device is /dev/wacom (**) stylus is in absolute mode (**) stylus: forcing TabletPC ISD V4 protocol (**) WACOM: suppress value is 2 (**) Option BaudRate 9600 (**) stylus: serial speed 9600 (**) Option SendCoreEvents (**) cursor: always reports core events (**) cursor device is /dev/wacom (**) cursor is in relative mode (**) cursor: forcing TabletPC ISD V4 protocol (**) WACOM: suppress value is 2 (**) Option BaudRate 9600 (**) cursor: serial speed 9600 (**) Option SendCoreEvents (**) eraser: always reports core events (**) eraser device is /dev/wacom (**) eraser is in absolute mode So... Both the stylus and the eraser are in absolute mode, but the cursor is not. So I tried the eraser, expecting it to be in 'real' absolute mode... but no. The problem remains. 'Absolute' mode just seems to be buggy. - - As always, if more info is needed, I'll happily submit it. -- /dev/wacom should be /dev/input/wacom in xorg.conf for USB tablets by default https://bugs.launchpad.net/bugs/117170 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 131833] [Gutsy tribe 4] video playback blanks / corrupts when displaying other items
Public bug reported: Binary package hint: compiz When I play a video (experience Ubuntu.ogg for example) in Totem on Gutsy tribe 4 live CD, the output is black by default, but when I move / resize the window the output returns back to normal for an instance until I stop moving the window. When changing the Desktop Effects setting to 'Extra effects' (and ignoring the 'nvidia hardware not available' popup), the video output is better (video returns as soon as I move / resize the window a bit or switch to fullscreen). But as soon as the system draws some other item on screen (popup hints, buttons, menus), the output goes black again or corrupts. See screenshot. When I set the Desktop Effects setting to 'No effects', the video output is fine, which makes me suspect the compiz package being the cause of this problem. Hardware: Toshiba Satellite Pro L10 (Intel 855GM graphics) ** Affects: compiz (Ubuntu) Importance: Undecided Status: New -- [Gutsy tribe 4] video playback blanks / corrupts when displaying other items https://bugs.launchpad.net/bugs/131833 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 131833] Re: [Gutsy tribe 4] video playback blanks / corrupts when displaying other items
** Attachment added: corrupted video output http://launchpadlibrarian.net/8782297/Screenshot-Experience%20ubuntu.ogg.png -- [Gutsy tribe 4] video playback blanks / corrupts when displaying other items https://bugs.launchpad.net/bugs/131833 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 131833] Re: [Gutsy tribe 4] video playback blanks / corrupts when displaying other items
*** This bug is a duplicate of bug 122979 *** https://bugs.launchpad.net/bugs/122979 Yes, it seems like it, although I had hoped / expected this bug would have been fixed in Gutsy (especially since Gutsy has composite-by-default). I do think this is a showstopper for Gutsy. Perhaps Totem is the right package to file this bug against, I don't know. Marked as a duplicate of #122979. ** This bug has been marked a duplicate of bug 122979 [aiglx][intel][r300] Video playback is buggy under Compiz -- [Gutsy tribe 4] video playback blanks / corrupts when displaying other items https://bugs.launchpad.net/bugs/131833 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 131635] [Gutsy tribe 4] usplash set manually to 1024x768 results in blank screen
Public bug reported: Binary package hint: libusplash0 When I: 1) boot into Gutsy tribe 4 using the live CD on my Toshiba Satellite Pro L10 (Intel 815 graphics) and I 2) manually set the VGA settings to 1024x768x24bbp using F4, and then continue to boot, then 3) Ubuntu boots but the screen remains blank until X starts. -When keeping the VGA setting at it's default setting, this problem doesn't occur. -I suspect it's the usplash package responsible for this problem, but I'm not entirely sure. -This problem doens't occur when I follow the steps above using a Feisty live CD, a.k.a. - this is a regression. ** Affects: usplash (Ubuntu) Importance: Undecided Status: New -- [Gutsy tribe 4] usplash set manually to 1024x768 results in blank screen https://bugs.launchpad.net/bugs/131635 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 77456] Re: Logitech Quickcam Fusion doesn't work
Nate, My apologies for yelling at you, that surely wasn't how I meant it :) Knowing now that you're actually not a hotshot bugfixer, I should indeed take matters more lightly. Thanks for contributing to this bugreport anyway, hopefully it will help in fixing this issue anytime soon. If anyone of the Ubuntu team is listening: perhaps it would be a good idea to put a bounty on this issue? Maybe that would allow the linux-uvc guys to fix this issue before Gutsy is released. -- Logitech Quickcam Fusion doesn't work https://bugs.launchpad.net/bugs/77456 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 117170] Re: Wacom pointer not absolute by default
Thanks again for your input, Colin. I'll have to dive into this issue again in 3 weeks when I come back from my holiday, but a quick look at xidump shows the following: [EMAIL PROTECTED]:~$ xidump stylus Unable to find input device 'stylus' [EMAIL PROTECTED]:~$ xidump -l Configured Mouse disabled Generic Keyboard keyboard Not good! Perhaps this has to do with the /dev/input/wacom thing you're mentioning. I'm gonna try this when I get back. I'm also wondering why Ubuntu doesn't have a graphical version of the xsetwacom tool (I know it exists)... Fiddling with these options in a terminal is simply annoying. More info in three weeks. Cheers! -- Wacom pointer not absolute by default https://bugs.launchpad.net/bugs/117170 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 117170] Re: extra options in xorg.conf
Thanks for your reply, Colin. I tried your suggestion, but it didn't make any difference. I guess the title of this bug is somewhat misleading, as both the stylus and the eraser _are_ both actually in absolute mode (Xorg.0.log clearly states so as mentioned in the bugreport addendum). My problem is that the 'absolute' mode is simply not working properly. This probably isn't much of an issue when your using the Wacom as a drawing tool, but when using it as a complete replacement for the mouse like I do (got some heavy RSI-problems here, using a pen instead of a mouse really helps) it's very annoying. I constantly have to 'recalibrate' the stylus as it reaches the end of the tablet when the cursor actually is not at the edge of the screen yet. These 'deviations' can become as bad as a quarter of the screen. Guess only very few people have this problem or bother if they do... :-( -- Wacom pointer not absolute by default https://bugs.launchpad.net/bugs/117170 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 77456] Re: Logitech Quickcam Fusion doesn't work
Too bad this bug is being shoved off with status 'not our problem'. While this may be true from a developers point of view, to the ordinary user it's simply: 'My cam don't work with this Ubuntu thing. With Windows it does. Ergo: Windows rules / Ubuntu sucks'. This is not helping in fixing bug #1. And quite frankly, I much sooner expect you and/or the maintainers of the kernel source package to do the talking with the linux-uvc guys since you/they know a LOT more about these things than we ordinary users do. Besides, I have a feeling they'd be a lot more sensitive to hear comment like that coming from people how actually know what they're talking about. Keep those lines short and please don't shove user's problems back to the people who report them. I'm not reopening this bug but I'm politely asking you to reconsider and try to solve this bug in a proactive way. Thanks. -- Logitech Quickcam Fusion doesn't work https://bugs.launchpad.net/bugs/77456 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 36252] how Kubuntu does it
*** This bug is a duplicate of bug 63090 *** https://bugs.launchpad.net/bugs/63090 Alan, I ejected (allthough it's called 'safely unmount' in Kubuntu Feisty) an external USB harddrive with an ext3 filesystem. It worked exactly as expected: -The drive spun down and stopped -The icon disappeared from the desktop -The drive was no longer accessible I believe this is how the 'eject' funtion in Nautilus should work as well (although I'm not sure how I would want it to behave if I had several partitions on my external drive... probably I would want the system to be smart enough to notice the difference between partitions on a disk and the disk itself. And give two options when I right click on one of those partitions on the desktop: 1) 'Unmount this partition on drive [foo]' and 2) 'Eject entire drive [foo]', followed by a popup, warning the user which partitions will also be unmounted when he/she continues. Or something similar, but this would probably be something for a blueprint? :-) ...). -- desktop/nautilus right-click eject problem for external usb disk and memory card reader https://bugs.launchpad.net/bugs/36252 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 36252] Kubuntu works fine
Perhaps irrelevant (allthough not to the end user) but I noticed Kubuntu 7.04 doesn't have this problem, which would confirm it's a nautilus-only issue. And I completely agree with Alexandre - this is very bad publicity for Ubuntu. -- desktop/nautilus right-click eject problem for external usb disk and memory card reader https://bugs.launchpad.net/bugs/36252 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 117170] Re: Wacom pointer not absolute by default
Is there anyone out there who experiences this same issue? If it can't be fixed, does anyone know of a workaround for this problem? ** Description changed: My problem with my Wacom Graphire USB is similar to bug #44279, and has been existing in every Ubuntu release so far where the tablet would work out of the box, including Feisty. Steps to reproduce, partially quoting from bug #44279, adjusted to my situation: 1. Boot any Ubuntu release with Wacom support 2. Plug in the Wacom Graphire tablet (I expect other graphire tablets to exhibit the same problem). 3. Place the Wacom pen in the top left position on the tablet. 4. The mouse pointer should move to the top left corner of the screen. 5. Move the pen diagonally across the tablet towards the lower right corner. Stop when the pen reaches the lower right corner of the tablet. Observe that the mouse pointer has not yet reached the lower right corner of the screen. What you see here is a failed attempt at using absolute positioning. What it looks like is an attempt to translate purely relative positioning into an absolute position much like navigation by dead reckoning. Unfortunately there seems to be a large deviation. This issue is quite annoying for someone working with a tablet, especially since aside from the underrun I describe here, there's also an overrun effect from time to time, where the mouse pointer has already reached the edge of the screen whereas the pen has not yet reached the end of the tablet (main description from bug #44279). There's no telling which one of the two effects will happen when, it seems random and they are both very annoying. One thing this bug does NOT share with bug #44279, is the reference to bug #44274, that seems to be / have been a different problem which I'm not experiencing. - Also, the situation has become worse in Feisty - after booting the Wacom - doesn't work by default. I have to plug it out and back in again in - order to make it work. I've submitted bug #117169 for that. - As always, if more info is needed, I'll happily submit it. -- Wacom pointer not absolute by default https://bugs.launchpad.net/bugs/117170 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 117169] Re: [Obsolete] Wacom tablet not recognized at boot
not a problem anymore. ** Summary changed: - Wacom tablet not recognized at boot + [Obsolete] Wacom tablet not recognized at boot ** Description changed: + Update: I don't know what's changed, but since a couple of weeks this problem just isn't happening anymore. Please mark as closed / obsolete. + However, bugs #44279 and #117170 still apply. + + Original report: + Since Feisty, when I boot Ubuntu, my Wacom Graphire USB tablet isn't recognized / turned on. I have to manually unplug the device and plug it back in. Then it works fine, except for the annoyance described in bug #44279 and bug #117170. ** Changed in: wacom-tools (Ubuntu) Status: New = Invalid -- [Obsolete] Wacom tablet not recognized at boot https://bugs.launchpad.net/bugs/117169 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 117170] Re: Wacom pointer not absolute by default
** Description changed: My problem with my Wacom Graphire USB is similar to bug #44279, and has been existing in every Ubuntu release so far where the tablet would work out of the box, including Feisty. Steps to reproduce, partially quoting from bug #44279, adjusted to my situation: 1. Boot any Ubuntu release with Wacom support 2. Plug in the Wacom Graphire tablet (I expect other graphire tablets to exhibit the same problem). 3. Place the Wacom pen in the top left position on the tablet. 4. The mouse pointer should move to the top left corner of the screen. 5. Move the pen diagonally across the tablet towards the lower right corner. Stop when the pen reaches the lower right corner of the tablet. Observe that the mouse pointer has not yet reached the lower right corner of the screen. What you see here is a failed attempt at using absolute positioning. What it looks like is an attempt to translate purely relative positioning into an absolute position much like navigation by dead reckoning. Unfortunately there seems to be a large deviation. This issue is quite annoying for someone working with a tablet, especially since aside from the underrun I describe here, there's also an overrun effect from time to time, where the mouse pointer has already reached the edge of the screen whereas the pen has not yet reached the end of the tablet (main description from bug #44279). There's no telling which one of the two effects will happen when, it seems random and they are both very annoying. One thing this bug does NOT share with bug #44279, is the reference to bug #44274, that seems to be / have been a different problem which I'm not experiencing. + Update: I checked the wacom manpage, which mentions this: + + Option Mode Relative|Absolute +sets the mode of the device. + + I brief 'hurray, found it!' moment flashed my mind. However, when I + looked at /var/log/Xorg.0.log I noticed this: + + (**) stylus device is /dev/wacom + (**) stylus is in absolute mode + (**) stylus: forcing TabletPC ISD V4 protocol + (**) WACOM: suppress value is 2 + (**) Option BaudRate 9600 + (**) stylus: serial speed 9600 + (**) Option SendCoreEvents + (**) cursor: always reports core events + (**) cursor device is /dev/wacom + (**) cursor is in relative mode + (**) cursor: forcing TabletPC ISD V4 protocol + (**) WACOM: suppress value is 2 + (**) Option BaudRate 9600 + (**) cursor: serial speed 9600 + (**) Option SendCoreEvents + (**) eraser: always reports core events + (**) eraser device is /dev/wacom + (**) eraser is in absolute mode + + So... Both the stylus and the eraser are in absolute mode, but the + cursor is not. So I tried the eraser, expecting it to be in 'real' + absolute mode... but no. The problem remains. 'Absolute' mode just seems + to be buggy. + As always, if more info is needed, I'll happily submit it. -- Wacom pointer not absolute by default https://bugs.launchpad.net/bugs/117170 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 119911] Re: Does not play mov in browser
Have you tried installing codecs from the Medibuntu archive (www.medibuntu.org)? Perhaps that helps... -- Does not play mov in browser https://bugs.launchpad.net/bugs/119911 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 119891] Re: choppy video playback
Well... this file plays perfectly here in both Mplayer and Totem. I must admit I have a slightly more powerfull configuration (AMD64 3200+, 1GB ram, Geforce 7600), I didn't notice any choppy playback whatsoever. The videofile itself looks blocky when displayed fullscreen, but I suppose that's logical for a 2 minute video in only 4,6MB. I'd take a look at your codecs, perhaps installing codecs from the Medibuntu archive (www.medibuntu.org) could help, if you haven't already done so. Furthermore, have you tried different players (mplayer / vlc / xine)? Do they make any difference? And what about other formats (mpeg2, mpeg1 etc.), do they play choppy as well? -- choppy video playback https://bugs.launchpad.net/bugs/119891 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 119911] Re: Does not play mov in browser
The URL you mentioned plays fine (although it's interlaced and totem refuses to de-interlace) on my setup (Ubuntu Feisty, totem)... Please provide more info on your setup, which Ubuntu version are you runnining, for example? ** Changed in: totem (Ubuntu) Status: Unconfirmed = Needs Info -- Does not play mov in browser https://bugs.launchpad.net/bugs/119911 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 119910] Re: Gnome should remember panel order and state
I've experienced this behavior many times before. Also, watch what happens if an application (especially games in wine) messes with the screen resolution - the order of panel items becomes a total mess. Confirmed. ** Changed in: meta-gnome2 (Ubuntu) Status: Unconfirmed = Confirmed -- Gnome should remember panel order and state https://bugs.launchpad.net/bugs/119910 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 119774] Re: allow the use authenticated smb shares without editing /ect/fstab
I totally agree on this one. Integrating an Ubuntu desktop in an existing Windows networking environment is simply painfull at the moment and seriously slows Ubuntu adoption in a Windows-dominated world. And by that, it's slowing progress on fixing bug #1. Confirmed. ** Changed in: gnome-vfs2 (Ubuntu) Sourcepackagename: None = gnome-vfs2 Status: Unconfirmed = Confirmed -- allow the use authenticated smb shares without editing /ect/fstab https://bugs.launchpad.net/bugs/119774 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 119886] Re: Evolution loses connection with microsoft exchange server
I've experienced similar errors when connecting to the exchange 2003 server at work. Especially when trying to browse the contacts stored in the Exchange database (this worked a lot better in Edgy!). Confirmed. ** Changed in: evolution (Ubuntu) Status: Unconfirmed = Confirmed -- Evolution loses connection with microsoft exchange server https://bugs.launchpad.net/bugs/119886 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 119891] Re: choppy video playback
This could be anything... badly encoded video files, poor hardware support, codec problems... Please provide more info (system specs / videocard + used driver) and perhaps upload a _small_ sample of the problematic file or put it on a public server where we can download it to check for ourselves. ** Changed in: totem (Ubuntu) Status: Unconfirmed = Needs Info -- choppy video playback https://bugs.launchpad.net/bugs/119891 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 116650] Re: Imation Disc Stakka C10AI goes wild when connected to PC
Brian, Here you go... the output of lsusb. ** Attachment added: output of lsusb http://launchpadlibrarian.net/7919040/lsusb.txt -- Imation Disc Stakka C10AI goes wild when connected to PC https://bugs.launchpad.net/bugs/116650 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 116650] Re: Imation Disc Stakka C10AI goes wild when connected to PC
...and the output of sudo lspci -vvn. And thanks for replying to my bugreport! ** Attachment added: output of sudo lspci -vvn http://launchpadlibrarian.net/7919053/sudo_lspci_-vvn.txt -- Imation Disc Stakka C10AI goes wild when connected to PC https://bugs.launchpad.net/bugs/116650 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 117170] Wacom pointer not absolute by default
Public bug reported: My problem with my Wacom Graphire USB is similar to bug #44279, and has been existing in every Ubuntu release so far where the tablet would work out of the box, including Feisty. Steps to reproduce, partially quoting from bug #44279, adjusted to my situation: 1. Boot any Ubuntu release with Wacom support 2. Plug in the Wacom Graphire tablet (I expect other graphire tablets to exhibit the same problem). 3. Place the Wacom pen in the top left position on the tablet. 4. The mouse pointer should move to the top left corner of the screen. 5. Move the pen diagonally across the tablet towards the lower right corner. Stop when the pen reaches the lower right corner of the tablet. Observe that the mouse pointer has not yet reached the lower right corner of the screen. What you see here is a failed attempt at using absolute positioning. What it looks like is an attempt to translate purely relative positioning into an absolute position much like navigation by dead reckoning. Unfortunately there seems to be a large deviation. This issue is quite annoying for someone working with a tablet, especially since aside from the underrun I describe here, there's also an overrun effect from time to time, where the mouse pointer has already reached the edge of the screen whereas the pen has not yet reached the end of the tablet (main description from bug #44279). There's no telling which one of the two effects will happen when, it seems random and they are both very annoying. One thing this bug does NOT share with bug #44279, is the reference to bug #44274, that seems to be / have been a different problem which I'm not experiencing. Also, the situation has become worse in Feisty - after booting the Wacom doesn't work by default. I have to plug it out and back in again in order to make it work. I've submitted bug #117169 for that. As always, if more info is needed, I'll happily submit it. ** Affects: wacom-tools (Ubuntu) Importance: Undecided Status: Unconfirmed -- Wacom pointer not absolute by default https://bugs.launchpad.net/bugs/117170 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 117169] Wacom tablet not recognized at boot
Public bug reported: Since Feisty, when I boot Ubuntu, my Wacom Graphire USB tablet isn't recognized / turned on. I have to manually unplug the device and plug it back in. Then it works fine, except for the annoyance described in bug #44279 and bug #117170. ** Affects: wacom-tools (Ubuntu) Importance: Undecided Status: Unconfirmed ** Description changed: Since Feisty, when I boot Ubuntu, my Wacom Graphire USB tablet isn't recognized / turned on. I have to manually unplug the device and plug it back in. Then it works fine, except for the annoyance described in bug - #44279. + #44279 and #117170 ** Description changed: Since Feisty, when I boot Ubuntu, my Wacom Graphire USB tablet isn't recognized / turned on. I have to manually unplug the device and plug it back in. Then it works fine, except for the annoyance described in bug - #44279 and #117170 + #44279 and bug #117170. -- Wacom tablet not recognized at boot https://bugs.launchpad.net/bugs/117169 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 44279] Re: Wacom tablet absolute positioning shifts around
*** This bug is a duplicate of bug 44274 *** https://bugs.launchpad.net/bugs/44274 This bug has been in every Ubuntu release so far, where my Wacom Graphire would work out of the box, including Feisty. I've submitted bug #117169 to elaborate on this. In Feisty, it's getting worse, though, please check bug #117170 about this. ** Changed in: wacom-tools (Ubuntu) Status: Unconfirmed = Confirmed -- Wacom tablet absolute positioning shifts around https://bugs.launchpad.net/bugs/44279 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 44279] Re: Wacom tablet absolute positioning shifts around
*** This bug is a duplicate of bug 44274 *** https://bugs.launchpad.net/bugs/44274 Whoops, there's a bug in my bugreport ;) - My comment should have been: This bug has been in every Ubuntu release so far, where my Wacom Graphire would work out of the box, including Feisty. I've submitted bug #117170 to elaborate on this. In Feisty, it's getting worse, though, please check bug #117169 about this. -- Wacom tablet absolute positioning shifts around https://bugs.launchpad.net/bugs/44279 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 116650] Imation Disc Stakka C10AI goes wild when connected to PC
Public bug reported: In Ubuntu 7.04 (booted from LiveCD), the Imation Disc Stakka C10AI (more info about this device on http://www.imation.com/products/disc_stakka/index.html ) goes wild when connected to the USB port of the PC. The 'dmesg' command shows this flood of messages: [ 494.856461] usb 1-2: new low speed USB device using uhci_hcd and address 71 [ 495.036505] usb 1-2: configuration #1 chosen from 1 choice [ 497.391046] usb 1-2: USB disconnect, address 71 [ 497.630854] usb 1-2: new low speed USB device using uhci_hcd and address 72 [ 497.810241] usb 1-2: configuration #1 chosen from 1 choice [ 500.665141] usb 1-2: USB disconnect, address 72 [ 500.936925] usb 1-2: new low speed USB device using uhci_hcd and address 73 [ 501.116579] usb 1-2: configuration #1 chosen from 1 choice [ 503.435519] usb 1-2: USB disconnect, address 73 The number just keeps going up and the message is repeated endlessly. Meanwhile, the Disc Stakka keeps making noises (sounds like it's trying to grab a disc, but fails over and over and over). If any more info is needed, I'll happily supply. ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Imation Disc Stakka C10AI goes wild when connected to PC https://bugs.launchpad.net/bugs/116650 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 116662] Re: screen output is corrupted on Dell OptiPlex GX115 and GX150
** Description changed: When running Ubuntu 7.04 from the live CD, the screen is corrupted when running at [EMAIL PROTECTED], the connected display's native resolution. - The corruption shows as 9 purple/blue 'fuzzing' vertical lines running + The corruption shows as 9 'fuzzing' vertical lines with varying colors + (different distortion colors on different background colors) running from the top to the bottom of the screen, approximately 3cm apart from each other, with a slightly larger gap of about 6cm between the 5th and 6th line from the left. The lines are invisible on a white or black background, and fully visible on the default background. On a full black background, or the default background, additional, intermitting white distortion is visible when moving the mouse (??!!). Things I've excluded as possible causes for this corruption: -The screen: I've tried 2 different LCD screens, a Dell 1703FPs and a HP1755 -The VGA cable: I've tried another, much thicker VGA cable, didn't make any difference -Possible glitch in one single PC: the problem exists in both the GX115 and the GX150, whereas the problem doesn't exist when running Windows on the same machine, at the same resolution. The corruption disappears when lowering the resolution to 1024x768. Output of 'sudo lshw' on the GX115 (I'll add the output of the GX150 as well, if desired): ubuntu description: Low Profile Desktop Computer product: OptiPlex GX115 vendor: Dell Computer Corporation serial: MFET8 width: 32 bits capabilities: smbios-2.3 dmi-2.3 configuration: administrator_password=enabled boot=normal chassis=low-profile frontpanel_password=enabled power-on_password=enabled uuid=44454C4C-00D7-104D-8046-80C04F455438 *-core description: Motherboard product: OptiPlex GX115 vendor: Dell Computer Corporation physical id: 0 *-firmware description: BIOS vendor: Dell Computer Corporation physical id: 0 version: A03 (11/03/2000) size: 64KB capacity: 448KB capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect edd int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification netboot *-cpu description: CPU product: Pentium III (Coppermine) vendor: Intel Corp. physical id: 400 bus info: [EMAIL PROTECTED] version: 6.8.6 slot: Microprocessor size: 933MHz capacity: 1600MHz width: 32 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up *-cache:0 description: L1 cache physical id: 700 size: 32KB capacity: 32KB capabilities: internal varies unified *-cache:1 description: L2 cache physical id: 701 size: 256KB capacity: 256KB capabilities: internal varies unified *-memory description: System Memory physical id: 1000 slot: System board or motherboard size: 512MB capacity: 512MB *-bank:0 description: DIMM SDRAM Synchronous 133 MHz (7.5 ns) physical id: 0 slot: DIMM_A size: 256MB width: 64 bits clock: 133MHz (7.5ns) *-bank:1 description: DIMM SDRAM Synchronous 133 MHz (7.5 ns) physical id: 1 slot: DIMM_B size: 256MB width: 64 bits clock: 133MHz (7.5ns) *-pci description: Host bridge product: 82815 815 Chipset Host Bridge and Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: [EMAIL PROTECTED]:00.0 version: 02 width: 32 bits clock: 33MHz *-display description: VGA compatible controller product: 82815 CGC [Chipset Graphics Controller] vendor: Intel Corporation physical id: 2 bus info: [EMAIL PROTECTED]:02.0 version: 02 size: 64MB width: 32 bits clock: 66MHz capabilities: vga bus_master cap_list configuration: driver=i810_smbus latency=0 resources: iomemory:f800-fbff iomemory:ff00-ff07 irq:9 *-pci description: PCI bridge product: 82801 PCI Bridge vendor: Intel Corporation
[Bug 116662] screen output is corrupted on Dell OptiPlex GX115 and GX150
Public bug reported: When running Ubuntu 7.04 from the live CD, the screen is corrupted when running at [EMAIL PROTECTED], the connected display's native resolution. The corruption shows as 9 purple/blue 'fuzzing' vertical lines running from the top to the bottom of the screen, approximately 3cm apart from each other, with a slightly larger gap of about 6cm between the 5th and 6th line from the left. The lines are invisible on a white or black background, and fully visible on the default background. On a full black background, or the default background, additional, intermitting white distortion is visible when moving the mouse (??!!). Things I've excluded as possible causes for this corruption: -The screen: I've tried 2 different LCD screens, a Dell 1703FPs and a HP1755 -The VGA cable: I've tried another, much thicker VGA cable, didn't make any difference -Possible glitch in one single PC: the problem exists in both the GX115 and the GX150, whereas the problem doesn't exist when running Windows on the same machine, at the same resolution. The corruption disappears when lowering the resolution to 1024x768. Output of 'sudo lshw' on the GX115 (I'll add the output of the GX150 as well, if desired): ubuntu description: Low Profile Desktop Computer product: OptiPlex GX115 vendor: Dell Computer Corporation serial: MFET8 width: 32 bits capabilities: smbios-2.3 dmi-2.3 configuration: administrator_password=enabled boot=normal chassis=low-profile frontpanel_password=enabled power-on_password=enabled uuid=44454C4C-00D7-104D-8046-80C04F455438 *-core description: Motherboard product: OptiPlex GX115 vendor: Dell Computer Corporation physical id: 0 *-firmware description: BIOS vendor: Dell Computer Corporation physical id: 0 version: A03 (11/03/2000) size: 64KB capacity: 448KB capabilities: isa pci pnp apm upgrade shadowing escd cdboot bootselect edd int13floppytoshiba int13floppy360 int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb ls120boot zipboot biosbootspecification netboot *-cpu description: CPU product: Pentium III (Coppermine) vendor: Intel Corp. physical id: 400 bus info: [EMAIL PROTECTED] version: 6.8.6 slot: Microprocessor size: 933MHz capacity: 1600MHz width: 32 bits capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 mmx fxsr sse up *-cache:0 description: L1 cache physical id: 700 size: 32KB capacity: 32KB capabilities: internal varies unified *-cache:1 description: L2 cache physical id: 701 size: 256KB capacity: 256KB capabilities: internal varies unified *-memory description: System Memory physical id: 1000 slot: System board or motherboard size: 512MB capacity: 512MB *-bank:0 description: DIMM SDRAM Synchronous 133 MHz (7.5 ns) physical id: 0 slot: DIMM_A size: 256MB width: 64 bits clock: 133MHz (7.5ns) *-bank:1 description: DIMM SDRAM Synchronous 133 MHz (7.5 ns) physical id: 1 slot: DIMM_B size: 256MB width: 64 bits clock: 133MHz (7.5ns) *-pci description: Host bridge product: 82815 815 Chipset Host Bridge and Memory Controller Hub vendor: Intel Corporation physical id: 100 bus info: [EMAIL PROTECTED]:00.0 version: 02 width: 32 bits clock: 33MHz *-display description: VGA compatible controller product: 82815 CGC [Chipset Graphics Controller] vendor: Intel Corporation physical id: 2 bus info: [EMAIL PROTECTED]:02.0 version: 02 size: 64MB width: 32 bits clock: 66MHz capabilities: vga bus_master cap_list configuration: driver=i810_smbus latency=0 resources: iomemory:f800-fbff iomemory:ff00-ff07 irq:9 *-pci description: PCI bridge product: 82801 PCI Bridge vendor: Intel Corporation physical id: 1e bus info: [EMAIL PROTECTED]:1e.0 version: 02 width: 32 bits clock: 33MHz capabilities: pci normal_decode bus_master *-network description: Ethernet interface product: 3c905C-TX/TX-M [Tornado] vendor: 3Com Corporation
[Bug 41831] Re: Openoffice in dapper has difficulties to redraw menus and icons
The problem is getting worse. This morning the problem was there again on my laptop which I use for work, so I checked for .gtk* files in my home dir. They existed (again) so I renamed them to *.old. Then I shut down the OOo quickstarter as before, restarted OOo... But the problem remained! I then tried to move the .gtk* files to another directory, repeating all other steps after that... but no success. So right now I'm stuck with a seriously degraded OOo installation. Kind of frustrating when you're bragging all day long to your colleagues about all the splendour of FLOSS/Ubuntu... :( In short - just removing .gtk* files from your home dir doesn't seem to fix this problem. -- Openoffice in dapper has difficulties to redraw menus and icons https://bugs.launchpad.net/bugs/41831 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 41831] Re: Openoffice in dapper has difficulties to redraw menus and icons
Bug still exists (and seems to be getting worse) in updated Ubuntu Feisty with both Ubuntu and Kubuntu-desktop packages installed. ** Changed in: openoffice.org (Ubuntu) Status: Fix Released = Confirmed -- Openoffice in dapper has difficulties to redraw menus and icons https://bugs.launchpad.net/bugs/41831 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 41831] Re: Openoffice in dapper has difficulties to redraw menus and icons
As noted on irc (and in this thread a few posts above), It's a fresh Kubuntu install with additionally ubuntu-desktop installed. New user, free drivers... I can imagine the problem not occuring when just using only a kubuntu or an ubuntu live cd, as I think my problem has to do with both KDE/qt and Gnome/gtk being installed. If I'm the only one experiencing this, I'd just like to state out I got this problem doing only standard stuff any ordinary user could/would. So potentially, everybody could experience my problem. I will however, create a(nother) new user and see if the problem persists. I'll also check if the problem remains when using KDE instead of Gnome. A reinstall of the system would take me too much time right now, but I'll try to figure out if I can replicate the problem when installing kubuntu-desktop on any other of my ubuntu machines. -- Openoffice in dapper has difficulties to redraw menus and icons https://bugs.launchpad.net/bugs/41831 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 41831] Re: Openoffice in dapper has difficulties to redraw menus and icons
Matthias, Removing the gtk-qt-engine package seems to have solved the problem. So the problem is in fact somehow related to some incompatibilities between qt and gtk? -- Openoffice in dapper has difficulties to redraw menus and icons https://bugs.launchpad.net/bugs/41831 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 41831] Re: Openoffice in dapper has difficulties to redraw menus and icons
I can confirm this bug still being present in Feisty, although it manifested itself only after a while. Feisty is installed here from a clean Kubuntu install, after which the ubuntu-desktop package was installed and gdm+gnome+metacity became the default environment (the reason why I installed it like this is IMHO irrelevant to this bugreport, however if anyone wants to know I'll happily elaborate). First I thought this problem had something to do with the desktop effects I had enabled, but turning them off didn't fix the problem. Renaming any .gtk* files in my home dir and then shutting down the OOo quickstarter did fix the problem. It seems that these .gtk* files are generated after a while and are causing problems. Which program/proces creates these files and why? My desktop seems to be happy without them (as a matter of fact, it seems to be better off without them!), so why generate them in the first place? I also created a theora/ogg video showing the problem clearly, if anyone's interested. -- Openoffice in dapper has difficulties to redraw menus and icons https://bugs.launchpad.net/bugs/41831 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 103790] confirmed
*** This bug is a duplicate of bug 99498 *** https://bugs.launchpad.net/bugs/99498 I also have this problem on 32bit Feisty. This bug seems to be a duplicate of https://bugs.launchpad.net/ubuntu/+source/hal/+bug/99498 and https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/102514 Can someone with the required privileges mark this one and the others? Maybe we should keep the discussion 'central' in the confirmed one, bug #99498, with the sidenote that having 2 or more partitions on the external drive doesn't seem to be relevant. ** This bug has been marked a duplicate of bug 99498 Nautilus and hal can't umount usb hd disk -- external USB HDD canno't unmout https://bugs.launchpad.net/bugs/103790 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 103790] possible workaround
*** This bug is a duplicate of bug 99498 *** https://bugs.launchpad.net/bugs/99498 A workaround can be found here: https://bugs.launchpad.net/ubuntu/+source/hal/+bug/99538/comments/6 I haven't tried it yet, can somebody please confirm? -- external USB HDD canno't unmout https://bugs.launchpad.net/bugs/103790 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 77456] Logitech Quickcam Fusion doesn't work
Public bug reported: As described in Bug #68468, the Logitech Quickcam Fusion doesn't work in Edgy. On http://mxhaard.free.fr/spca5xx.html it's pointed out that it could be supported when using the Linux-UVC driver. Unfortunately, the site hosting this driver seems unreachable at the moment (at least from my location). And Ubuntu doesn't seem to be using the Linux-UVC driver, nor does this driver seem to be installable through the 'normal' repositories. Ubuntu version: Edgy (6.10) Kernel: 2.6.17-10-generic Device: Logitech Quickcam Fusion (vendor ID 0x046d, product ID 0x08c1) Host PC: Dell Dimension 5000 ** Affects: Ubuntu Importance: Undecided Status: Unconfirmed -- Logitech Quickcam Fusion doesn't work https://launchpad.net/bugs/77456 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 77427] faulty channel mappings on Intel ICH6
Public bug reported: Binary package hint: gnome-volume-manager On a Dell Dimension 5000 with Intel ICH6 onboard audio, the 'Master' fader is mapped to the headphone output on the front of the system, while the 'Master Surround' fader is mapped to the line-out output on the rear of the system. Perhaps there are more faulty mappings, I haven't had time to check all possible settings / connections. Ubuntu version: Edgy (6.10) gnome-volume-manager version: 2.16.1 System: Dell Dimension 5000 lspci output: 00:00.0 Host bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Express Memory Controller Hub (rev 04) 00:01.0 PCI bridge: Intel Corporation 915G/P/GV/GL/PL/910GL Express PCI Express Root Port (rev 04) 00:02.0 VGA compatible controller: Intel Corporation 82915G/GV/910GL Express Chipset Family Graphics Controller (rev 04) 00:02.1 Display controller: Intel Corporation 82915G Express Chipset Family Graphics Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03) 00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3) 00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03) 00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03) 00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03) 00:1f.2 IDE interface: Intel Corporation 82801FB/FW (ICH6/ICH6W) SATA Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03) 04:03.0 Ethernet controller: Broadcom Corporation BCM4401 100Base-T (rev 01) If more info is needed, I'll happily submit it. ** Affects: gnome-volume-manager (Ubuntu) Importance: Undecided Assignee: DaveThacker Status: Needs Info -- faulty channel mappings on Intel ICH6 https://launchpad.net/bugs/77427 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 77427] Re: faulty channel mappings on Intel ICH6
I'm not with the system right now, but it's a default Edgy install. So that should mean it's ALSA, right? Matthijs / iGadget DaveThacker wrote: Thanks for reporting the bug. Which sound manager are you using? (Alsa..etc?) Dave Thacker ** Changed in: gnome-volume-manager (Ubuntu) Assignee: (unassigned) = DaveThacker Status: Unconfirmed = Needs Info -- faulty channel mappings on Intel ICH6 https://launchpad.net/bugs/77427 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
