[Bug 1785107] Re: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver
The choice of simply not using the flag with ghostscript is a false choice for most users, given ghostscript is used under the hood by a number of applications. A cursory search for the error message on the internet shows a number of related consequences, including pstoedit and inkscape which uses pstoedit. The notion that there's just a warning isn't true as well. The change breaks pstoedit. The broken pstoedit breaks inkscape (Export to SVG). This might well be bad code on the pstoedit side, but it's still a change that breaks the (relative) userspace. There's a description of what seems to have happened at https://bugs.launchpad.net/inkscape/+bug/1734624/comments/21 Specifically, the version of pstoedit included in 18.04 is not likely to be compatible with the included version of ghostscript. Applications depending on pstoedit will be broken on this release. Any other applications directly depending on ghostscript and using DELAYBIND might have similar trouble. The pstoedit folk added a workaround specific to ghostscript 9.22 in pstoedit 3.71. If pstoedit is bumped up to 3.71, it would be possible for direct users of pstoedit to workaround with -rdb. This would probably leave inkscape still broken because it uses pstoedit under the hood. Given 18.04 is an LTS, a solution does have to be found by and for Ubuntu 18.04, or both pstoedit and inkscape will have issues for the entire life of this release. The possible options I see are : * Upgrade ghostscript to 9.23, hopefully not resulting in any additional breakage. * Upgrade pstoedit to 3.71, so atleast the -rdb workaround will exist for direct users, but leaves inkscape partially broken. * Deal with ghostscipt upstream and find a way to patch in that one option back to 9.22, upgrade ghostscript to a patch release of 9.22. If DELAYBIND really does nothing useful, this should not be very difficult. However, the comments from their bugzilla listed above suggest ghostscript seems adamant this isn't their problem. * Deal with pstoedit upstream and find a way to patch 3.70 to include the -rdb workaround, upgrade to the next patch release of pstoedit, make users of it able to use pstoedit again even if inkscape remains broken. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785107 Title: Ghostscript and pstoedit versions not compatible in 18.04 Bionic Beaver To manage notifications about this bug go to: https://bugs.launchpad.net/pstoedit/+bug/1785107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672233] [NEW] Incorrect/inappropriate file associations
Public bug reported: Installing freecad on ubuntu results in incorrect file associations, including such files as below being attempted to be opened by freecad: - Text files without extension, such as "ChangeLog" - ".yaml" files. This results in rather poor, even annoying user experience. ** Affects: freecad (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/1672233 Title: Incorrect/inappropriate file associations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1672233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1605849] [NEW] libkmod2-dev:i386 fails to install on ubuntu 16.04 x64
Public bug reported:
Installing libkmod2-dev:i386 fails when the 64-bit version is also
installed. See below. The 'partially installed' package is because of a
previous aptitude install command which included many other packages
which first showed the error.
$ sudo aptitude install libudev-dev:i386
The following NEW packages will be installed:
libkmod2:i386{a}
The following partially installed packages will be configured:
libudev-dev:i386
0 packages upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/45.9 kB of archives. After unpacking 136 kB will be used.
Do you want to continue? [Y/n/?] Y
(Reading database ... 514830 files and directories currently installed.)
Preparing to unpack .../libkmod2_22-1ubuntu4_i386.deb ...
Unpacking libkmod2:i386 (22-1ubuntu4) ...
dpkg: error processing archive
/var/cache/apt/archives/libkmod2_22-1ubuntu4_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz',
which is different from other instances of package libkmod2:i386
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Errors were encountered while processing:
/var/cache/apt/archives/libkmod2_22-1ubuntu4_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package. Trying to recover:
dpkg: dependency problems prevent configuration of libudev-dev:i386:
libudev-dev:i386 depends on libkmod2 (>= 5~); however:
Package libkmod2:i386 is not installed.
dpkg: error processing package libudev-dev:i386 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libudev-dev:i386
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libkmod2 22-1ubuntu4 [modified:
usr/share/doc/libkmod2/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Sat Jul 23 14:55:19 2016
Dependencies:
gcc-6-base 6.0.1-0ubuntu1
libc6 2.23-0ubuntu3
libgcc1 1:6.0.1-0ubuntu1
DuplicateSignature:
package:libkmod2:22-1ubuntu4 [modified:
usr/share/doc/libkmod2/changelog.Debian.gz]
Unpacking libkmod2:i386 (22-1ubuntu4) ...
dpkg: error processing archive
/var/cache/apt/archives/libkmod2_22-1ubuntu4_i386.deb (--unpack):
trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz',
which is different from other instances of package libkmod2:i386
ErrorMessage: trying to overwrite shared
'/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other
instances of package libkmod2:i386
InstallationDate: Installed on 2014-04-18 (826 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.12~ubuntu16.04.1
SourcePackage: kmod
Title: package libkmod2 22-1ubuntu4 [modified:
usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying
to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is
different from other instances of package libkmod2:i386
UpgradeStatus: Upgraded to xenial on 2016-07-22 (1 days ago)
** Affects: kmod (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package package-conflict xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1605849
Title:
libkmod2-dev:i386 fails to install on ubuntu 16.04 x64
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1605849/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257909] Re: [pbuilder-dist] should honour BASETGZ or name consistently
Attached is the workaround I am presently using. It's as inflexible and specific as the original implementation, but atleast provides consistency and solves _my_ problem. ** Patch added: basetgz-string.diff https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1257909/+attachment/3927907/+files/basetgz-string.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257909 Title: [pbuilder-dist] should honour BASETGZ or name consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1257909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257909] [NEW] [pbuilder-dist] should honour BASETGZ or name consistantly
Public bug reported: When running pbuilder-dist dist arch create, pbuilder-dist creates the base tarball per hardcoded naming conventions. In doing so, it disregards the contents of ~/.pbuilderrc and also provides no easy workaround. When run on an amd64 system, pbuilder-dist saucy amd64 create pbuilder-dist saucy i386 create produces the following base tarballs : saucy-base.tgz saucy-i386-base.tgz These tarballs, consequently, have the following problems : 1. The names are inconsistent. Running the same commands on i386 and amd64 machines produces markedly different results, making other third-party helper tools and scripts harder to write. 2. The names are inconsistent with the names set out in ~/.pbuilderrc, specifically as BASETGZ 3. (My specific instance of trouble) rebuildd, for whatever reason, wants the tarballs as saucy-amd64.tgz and saucy-i386.tgz. I have no way to provide these without making (minor) modifications to /usr/bin/pbuilder-dist. This is alright, and one could argue that rebuildd should provide a nomenclature specification method, which it probably does, but I think that for the sake of convenience and consistent experience, pbuilder- dist should do one of more of the following: 1. Honor whatever is in ~/.pbuilderrc in terms of BASETGZ 2. Allow modification of BASETGZ with either an argument or using an environment variable to override whatever is hardcoded and/or whatever is in .pbuilderrc 3. Name the tarballs consistently by default. I expect there are various other dependencies involved, but I really don't see why arch should not just be included in the tgz name by default. The only possible explanation I can think of is if it is something used for truely arch-independent packaging (any), but that logic does not really support enforced arch-free naming for the host arch. ** Affects: ubuntu-dev-tools (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/1257909 Title: [pbuilder-dist] should honour BASETGZ or name consistantly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1257909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1257909] Re: [pbuilder-dist] should honour BASETGZ or name consistently
** Summary changed: - [pbuilder-dist] should honour BASETGZ or name consistantly + [pbuilder-dist] should honour BASETGZ or name consistently -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1257909 Title: [pbuilder-dist] should honour BASETGZ or name consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1257909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 916430] Re: Bug in ftdi_sio in linux 3.0.0-14-generic
Where / how would I start looking for a solution, if I were to try? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916430 Title: Bug in ftdi_sio in linux 3.0.0-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 916430] [NEW] Bug in ftdi_sio in linux 3.0.0-14-generic
Public bug reported: There seems to be a bug in the ftdi_sio driver shipped with ubuntu 11.10. I've been able to reproduce the bug on both 64-bit (x86_64) and 32 bit machines. The Problem : Connecting an FT2232H programmed to function in CPU FIFO mode in channel A to a ubuntu machine causes the driver to crash immediately. dmesg provides a long and, to me, incomprehensible trace which I've pasted below. Once this happens, I need to restart my computer before it does anything with an FTDI again. Possibly, forcing the ftdi_sio to unload would be sufficient, but I'm not certain how to achieve that effect. The lsusb entry for the FTDI also does not disappear after disconnection, and lsusb -v hangs, probably while trying to probe the device. This does not happen when the FT2232H is programmed to function as a dual UART (the default configuration). The same chip with the same configuration works fine on a machine running Fedora 14 with linux-2.6.35.6-45-fc14. How to reproduce : Plug in an FTDI FT2232H with channel configured in CPU FIFO mode. dmesg output : [ 4002.848065] usb 2-2: new high speed USB device number 6 using ehci_hcd [ 4002.984791] BUG: unable to handle kernel NULL pointer dereference at (null) [ 4002.988011] IP: [a05ee3ab] ftdi_8u2232c_probe+0x3b/0x80 [ftdi_sio] [ 4002.988011] PGD 0 [ 4002.988011] Oops: [#1] SMP [ 4002.988011] CPU 1 [ 4002.988011] Modules linked in: usb_storage uas hidp xt_conntrack iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables bnep rfcomm vboxnetadp vboxnetflt vboxdrv parport_pc ppdev binfmt_misc dm_crypt ftdi_sio usbserial joydev snd_hda_codec_idt snd_hda_codec_hdmi btusb uvcvideo videodev v4l2_compat_ioctl32 bluetooth snd_hda_intel snd_hda_codec snd_hwdep dell_wmi sparse_keymap snd_pcm snd_seq_midi dell_laptop dcdbas snd_rawmidi psmouse lib80211_crypt_tkip r592 r852 sm_common nand nand_ids nand_bch bch nand_ecc serio_raw memstick mtd wl(P) snd_seq_midi_event snd_seq lib80211 snd_timer snd_seq_device snd soundcore snd_page_alloc coretemp lp parport btrfs zlib_deflate libcrc32c usbhid hid ahci libahci i915 firewire_ohci sdhci_pci sdhci firewire_core wmi crc_itu_t drm_kms_helper sky2 drm i2c_algo_bit video [ 4002.988011] [ 4002.988011] Pid: 20, comm: khubd Tainted: P3.0.0-14-generic #23-Ubuntu Dell Inc. Inspiron 1525 /0U990C [ 4002.988011] RIP: 0010:[a05ee3ab] [a05ee3ab] ftdi_8u2232c_probe+0x3b/0x80 [ftdi_sio] [ 4003.023739] RSP: 0018:8800b90f3720 EFLAGS: 00010246 [ 4003.023739] RAX: a05ee370 RBX: 88004c3309c0 RCX: 000e [ 4003.023739] RDX: a05f5f80 RSI: RDI: a05f173a [ 4003.023739] RBP: 8800b90f3730 R08: 880076089000 R09: 88004c3309c0 [ 4003.023739] R10: R11: R12: 880076089000 [ 4003.023739] R13: a05f6000 R14: a05f2288 R15: 88004dd1cc00 [ 4003.023739] FS: () GS:8800bf50() knlGS: [ 4003.023739] CS: 0010 DS: ES: CR0: 8005003b [ 4003.023739] CR2: CR3: 85df2000 CR4: 000406e0 [ 4003.023739] DR0: DR1: DR2: [ 4003.023739] DR3: DR6: 0ff0 DR7: 0400 [ 4003.023739] Process khubd (pid: 20, threadinfo 8800b90f2000, task 8800b98bc560) [ 4003.023739] Stack: [ 4003.023739] 88004c3309c0 a05f2288 8800b90f3750 a05ee02e [ 4003.023739] a05f5c80 88004c3309c0 8800b90f3900 a05c8c7b [ 4003.023739] 8800bf512a40 0001 [ 4003.023739] Call Trace: [ 4003.023739] [a05ee02e] ftdi_sio_probe+0x2e/0x50 [ftdi_sio] [ 4003.023739] [a05c8c7b] usb_serial_probe+0x14b/0x12d0 [usbserial] [ 4003.023739] [812e9c10] ? ida_get_new_above+0x70/0x300 [ 4003.023739] [811d8fe8] ? sysfs_new_dirent+0x58/0x140 [ 4003.023739] [811d9273] ? sysfs_find_dirent+0x53/0x70 [ 4003.023739] [810329b9] ? default_spin_lock_flags+0x9/0x10 [ 4003.023739] [810329b9] ? default_spin_lock_flags+0x9/0x10 [ 4003.023739] [81451a73] usb_probe_interface+0xd3/0x1e0 [ 4003.023739] [813cf738] really_probe+0x68/0x190 [ 4003.023739] [813cf9c5] driver_probe_device+0x45/0x70 [ 4003.023739] [813cfaf3] __device_attach+0x53/0x60 [ 4003.023739] [813cfaa0] ? __driver_attach+0xb0/0xb0 [ 4003.023739] [813ce4ac] bus_for_each_drv+0x5c/0x90 [ 4003.023739] [813cf937] device_attach+0xa7/0xc0 [ 4003.023739] [813ceedd] bus_probe_device+0x2d/0x50 [ 4003.023739] [813ccfbf] device_add+0x2df/0x3e0 [ 4003.023739] [8144fef1] usb_set_configuration+0x5d1/0x6d0 [ 4003.023739] [811d91cb] ? sysfs_addrm_finish+0x1b/0x70 [ 4003.023739]
[Bug 916430] Re: Bug in ftdi_sio in linux 3.0.0-14-generic
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/916430 Title: Bug in ftdi_sio in linux 3.0.0-14-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 530858] Re: VLC with pulseaudio doesn't work
My bug ( https://bugs.edge.launchpad.net/ubuntu/+source/vlc/+bug/533039 ) was marked a duplicate of this one. Note that this bug report states that the problem disappears after a reboot, while mine does not. I get sound from vlc only if run as root or with the user in the audio group, which is not the default for *buntu lynx -- VLC with pulseaudio doesn't work https://bugs.launchpad.net/bugs/530858 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 533039] [NEW] No sound on vanilla kubuntu + vlc
Public bug reported: Binary package hint: vlc vlc on a vanilla kubuntu lucid install produces no sound unless run with sudo and the vlc-wrapper. problem is fixed when the user is added to the 'audio' group. This probably needs to be fixed in the default groups unless vlc can be made to go through pulseaudio (if i understand the general sound configuration correctly). version : 1.0.5-1ubuntu1 ** Affects: vlc (Ubuntu) Importance: Undecided Status: New -- No sound on vanilla kubuntu + vlc https://bugs.launchpad.net/bugs/533039 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 364359] Re: [i965] High %CPU/Power Usage unless downgrade to 2.4 (UXA/EXA)
The downgrade to 2..4 did not help me either. In fact, it made things worse. The bootm line is that cpu usage was minimal on 8.10, and immediately on upgrade to 9.04, the X process's cpu usage shot up to a time average of about 50% of one core (of a 2.0 GHz Core2Duo, 4 MB L2). Downgrading brought the time average cpu usage of the X process to around 80% of one core. While I see the merit in trying to narrow down the cause of the problem, I honestly dont buy the 'it must be some other problem that other people have' . The problem started in the same way for everybody, and its possible in a specific use case the older driver is able to avoid some other bug that was introduced. -- [i965] High %CPU/Power Usage unless downgrade to 2.4 (UXA/EXA) https://bugs.launchpad.net/bugs/364359 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 118574] Re: crash if i press F12
I can confirm that this happens on Ubuntu Gutsy with the nvidia drivers. I'm abe to reproduce it with more or less 100% accuracy. Open two tabs, with the second one active. Run some X-application from it (I'm not sure if its all or just a few - I've seen it happen with mplayer and deluge) and X crashes. The time taken to get back to the kdm/gdm varies from time to time. -- crash if i press F12 https://bugs.launchpad.net/bugs/118574 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
Re: [Bug 94813] Re: starting gparted mounts all devices
I think it is, yes. On 6/30/07, Peter Berry [EMAIL PROTECTED] wrote: dupe of bug 86851 ? -- starting gparted mounts all devices https://bugs.launchpad.net/bugs/94813 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 108488] Re: unable to login after suspension
Does your laptopt have an LED indicator of the Num-lock status? What happens if you try to turn it off by hitting the numlock key while the password box is visible? -- unable to login after suspension https://bugs.launchpad.net/bugs/108488 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 94813] Re: starting gparted mounts all devices
I can confirm that this is an issue, and a rather annoying one at that. The issue is not just with removable media. It does the same with all partitions on internal drives as well. I also thing gparted has something to do with it, and not hal as is suggested in similar bug reports. the problem does not occur with fdisk, or even parted. I am unable to use gparted for _any_ partitioning whatsoever. The best i can do is to see what my partition table looks like in the forms of coloured rectangles rather than a list of partitions and cylinders. The problem is serious - it makes the Gnome Partiion Manager useless and makes it hell to fiddle with your partitions, which is kindof a day-to- day issue for people who keep reinstalling their operating systems for the fun of it. -- starting gparted mounts all devices https://bugs.launchpad.net/bugs/94813 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 37768] Re: gnome-volume-manager mounting Partition, while working with GParted
The issue is not just with removable media. It does the same with all partitions on internal drives as well. I also thing gparted has something to do with it, and not hal. the problem does not occus with fdisk, or even parted. I am unable to use gparted for _any_ partitioning whatsoever. The best i can do is to see what my partition table looks like in the forms of coloured rectangles rather than a list of partitions and cylinders. THe problem is serious - it makes the Gnome Partiion Manager useless and makes it hell to fiddle with your partitions, which is kindof a day-to- day issue for people who keep reinstalling their operating systems for the fun of it. -- gnome-volume-manager mounting Partition, while working with GParted https://bugs.launchpad.net/bugs/37768 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 65552] Re: usb-drive is automaticly remounted during format stopping gparted
The problem is not fixed in feisty. Atleast, I have the same issue. Not with removable media though. I dont have a USB drive to test with right now. I have the problem with internal hard drives. All three of them show the same behaviour on 2 computers (with the same ubuntu install, only difference being a recofigure of xserver-xorg). None of the partitions are on the fstab. All of them automount in the middle of the creating of the new partition - just after the partition is created but before the new filesystem is written. This bug makes gparted useless as a partitioning tool. -- usb-drive is automaticly remounted during format stopping gparted https://bugs.launchpad.net/bugs/65552 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 119708] xen-source-2.6.19 missing?
Public bug reported: xen-source in the repositories seems to be pointing to the xen- source-2.6.16 package. Further, the xen-source-2.6.19 package (recommended by xen-image-2.6.19) is not found by aptitude. installing the ubuntu-xen-server package installs the xen kernel based on the 2.6.19 ubuntu server kernel. The following is my sources.list(without the comments) deb http://us.archive.ubuntu.com/ubuntu/ feisty main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ feisty main restricted deb http://us.archive.ubuntu.com/ubuntu/ feisty main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ feisty main restricted deb http://us.archive.ubuntu.com/ubuntu/ feisty-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ feisty-updates main restricted deb http://us.archive.ubuntu.com/ubuntu/ feisty universe deb-src http://us.archive.ubuntu.com/ubuntu/ feisty universe deb http://us.archive.ubuntu.com/ubuntu/ feisty multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ feisty multiverse deb http://us.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse deb-src http://us.archive.ubuntu.com/ubuntu/ feisty-backports main restricted universe multiverse deb http://security.ubuntu.com/ubuntu feisty-security main restricted deb-src http://security.ubuntu.com/ubuntu feisty-security main restricted deb http://security.ubuntu.com/ubuntu feisty-security universe deb-src http://security.ubuntu.com/ubuntu feisty-security universe deb http://security.ubuntu.com/ubuntu feisty-security multiverse deb-src http://security.ubuntu.com/ubuntu feisty-security multiverse deb http://medibuntu.sos-sts.com/repo/ feisty free non-free deb-src http://medibuntu.sos-sts.com/repo/ feisty free non-free deb http://archive.canonical.com/ubuntu feisty-commercial main deb http://edevelop.org/pkg-e/ubuntu feisty e17 deb http://e17.dunnewind.net/ubuntu feisty e17 deb-src http://edevelop.org/pkg-e/ubuntu feisty e17 deb http://gnomefreak.youmortals.com/mozilla-testing feisty main deb-src http://gnomefreak.youmortals.com/mozilla-testing feisty main deb http://www.telemail.fi/mlind/ubuntu feisty main deb http://kubuntu.org/packages/kde4-3.90.1/ feisty main ** Affects: xen-source (Ubuntu) Importance: Undecided Status: Unconfirmed -- xen-source-2.6.19 missing? https://bugs.launchpad.net/bugs/119708 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 96599] Re: letters disapers in tilda
This letter disappearing thing happens, and setting the double buffering works. Thanks eppy 1 I think that this happens only on certain hardware though. My laptop with the intel 851 chipset never had this issue, while my geforece8500GT with the nvidia beta drivers as well as with the vesa drivers -- letters disapers in tilda https://bugs.launchpad.net/bugs/96599 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
