[Bug 45026] Re: K3b dont find emovix-2 and normalize
After a few years I tried this function (normalize audio) and of course it doesn`t work because of the bug. Is this so difficult to correct this ? -- You received this bug notification because you are a member of Kubuntu Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/45026 Title: K3b dont find emovix-2 and normalize -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
Patch works for me. No additional problem. I also forced all 8 partitions to check. -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 571707] Re: fsck progress stalls at boot, plymouthd/mountall eats CPU
@letstrynl Patch should be issued very soon in official repo. My system has 8 partition. With this bug is almost unusable, because a have to wait many hours to log in. Running PC like server is not a solution. -- fsck progress stalls at boot, plymouthd/mountall eats CPU https://bugs.launchpad.net/bugs/571707 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 72908] Re: No sound with intel ALC262
Can anybody explain it to me. Does it work or not. I'm going to buy a laptop with this chip. What does it mean Supported in upstream git. Is this supported in Ubuntu 9.04 with current updates or not ? -- No sound with intel ALC262 https://bugs.launchpad.net/bugs/72908 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 358652] Re: Error during mysql slave replication
Because this bug disappear after some update probably may be closed. -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 358652] Re: Error during mysql slave replication
Because this bug disappear after some update probably may be closed. -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 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 295536] Re: cups-pdf fails bad status reported and no pdf created
I still have this problem on 9.04. It is a very short time to final release of Jaunty. -- cups-pdf fails bad status reported and no pdf created https://bugs.launchpad.net/bugs/295536 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 358652] Re: Error during mysql slave replication
** Description changed: After upgrading to jaunty I have problem with replication system in mysql. After every system reboot I have to issue RESET SLAVE; START SLAVE; command to continue this to work. The reason for that is fact that relays log have higher index number than number stored in mysqld- relay-bin.index. These two command simply reset that. What is even more interesting /etc/init.d/mysql restart doesn't generate mentioned problem. Description:Ubuntu jaunty (development branch) Release:9.04 mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 + + Updated info in comments -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 358652] Re: Error during mysql slave replication
** Description changed: After upgrading to jaunty I have problem with replication system in mysql. After every system reboot I have to issue RESET SLAVE; START SLAVE; command to continue this to work. The reason for that is fact that relays log have higher index number than number stored in mysqld- relay-bin.index. These two command simply reset that. What is even more interesting /etc/init.d/mysql restart doesn't generate mentioned problem. Description:Ubuntu jaunty (development branch) Release:9.04 mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 + + Updated info in comments -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 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 358652] Re: Error during mysql slave replication
Ok I did some additional tests and there is a time to give some result: First of all I am doing a master-master replication. On Ubuntu 8.04 my configuration works for months so I rather expect an error on Ubuntu 9.04 site. The problem is the configuration is almost the same (exludind server-id of cource). In addition I say I used new my.cnf file delivered with new version of mysql server in 9.04. My changes are: # bind-address = 127.0.0.1 # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. log = /var/log/mysql/mysql.log # # Error logging goes to syslog. This is a Debian improvement :) # # Here you can see queries with especially long duration #log_slow_queries = /var/log/mysql/mysql-slow.log #long_query_time = 2 #log-queries-not-using-indexes # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. server-id = 1 log_bin = /var/log/mysql/mysql-bin.log expire_logs_days= 10 max_binlog_size = 100M #binlog_ignore_db = include_database_name binlog_do_db= ... binlog_do_db= ... replicate-do-db=.. replicate-do-db=.. auto_increment_increment = 2 auto_increment_offset = 1 slave-skip-errors = 1062 Secondly after reboot In /var/lib/mysql/ cat relay-log.info ./mysqld-relay-bin.05 98 0 ls mysqld-relay-* mysqld-relay-bin.06 mysqld-relay-bin.07 mysqld-relay-bin.index So there is a inconsistency. After RESET SLAVE; START SLAVE;command info in relay-log.info and files are consistent. -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 358652] Re: Error during mysql slave replication
Ok I did some additional tests and there is a time to give some result: First of all I am doing a master-master replication. On Ubuntu 8.04 my configuration works for months so I rather expect an error on Ubuntu 9.04 site. The problem is the configuration is almost the same (exludind server-id of cource). In addition I say I used new my.cnf file delivered with new version of mysql server in 9.04. My changes are: # bind-address = 127.0.0.1 # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. log = /var/log/mysql/mysql.log # # Error logging goes to syslog. This is a Debian improvement :) # # Here you can see queries with especially long duration #log_slow_queries = /var/log/mysql/mysql-slow.log #long_query_time = 2 #log-queries-not-using-indexes # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. server-id = 1 log_bin = /var/log/mysql/mysql-bin.log expire_logs_days= 10 max_binlog_size = 100M #binlog_ignore_db = include_database_name binlog_do_db= ... binlog_do_db= ... replicate-do-db=.. replicate-do-db=.. auto_increment_increment = 2 auto_increment_offset = 1 slave-skip-errors = 1062 Secondly after reboot In /var/lib/mysql/ cat relay-log.info ./mysqld-relay-bin.05 98 0 ls mysqld-relay-* mysqld-relay-bin.06 mysqld-relay-bin.07 mysqld-relay-bin.index So there is a inconsistency. After RESET SLAVE; START SLAVE;command info in relay-log.info and files are consistent. -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 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 358652] [NEW] Error during mysql slave replication
Public bug reported: After upgrading to jaunty I have problem with replication system in mysql. After every system reboot I have to issue RESET SLAVE; START SLAVE; command to continue this to work. The reason for that is fact that relays log have higher index number than number stored in mysqld- relay-bin.index. These two command simply reset that. What is even more interesting /etc/init.d/mysql restart doesn't generate mentioned problem. Description:Ubuntu jaunty (development branch) Release:9.04 mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrading to jaunty I have problem with replication system in mysql. After every system reboot I have to issue RESET SLAVE; START SLAVE; command to continue this to work. The reason for that is fact that relays log have higher index number than number stored in mysqld- relay-bin.index. These two command simply reset that. What is even more - interesting /etc/init.d/mysql restart works ok. + interesting /etc/init.d/mysql restart doesn't generate mentioned + problem. Description:Ubuntu jaunty (development branch) Release:9.04 mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 358652] [NEW] Error during mysql slave replication
Public bug reported: After upgrading to jaunty I have problem with replication system in mysql. After every system reboot I have to issue RESET SLAVE; START SLAVE; command to continue this to work. The reason for that is fact that relays log have higher index number than number stored in mysqld- relay-bin.index. These two command simply reset that. What is even more interesting /etc/init.d/mysql restart doesn't generate mentioned problem. Description:Ubuntu jaunty (development branch) Release:9.04 mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New ** Description changed: After upgrading to jaunty I have problem with replication system in mysql. After every system reboot I have to issue RESET SLAVE; START SLAVE; command to continue this to work. The reason for that is fact that relays log have higher index number than number stored in mysqld- relay-bin.index. These two command simply reset that. What is even more - interesting /etc/init.d/mysql restart works ok. + interesting /etc/init.d/mysql restart doesn't generate mentioned + problem. Description:Ubuntu jaunty (development branch) Release:9.04 mysql-server-5.0 5.1.30really5.0.75-0ubuntu10 -- Error during mysql slave replication https://bugs.launchpad.net/bugs/358652 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 288494] Re: the youtube code needs to be updated
If you think that problem is solved than you are wrong. There is still no official backport to hardy (3 year support isn`t it). Downloading some files from 3rd person place is no a solution to that problem. -- the youtube code needs to be updated https://bugs.launchpad.net/bugs/288494 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 205884] Re: mouse over an *.avi video file and konqueror crashes
If there is a fix to this then why I can see problem described above ? I am keeping system fully updated. This error occurs when I put my mouse over any media file and move it away too quickly. Sound begin to appear and after this nothing happens. The only way is to restart all kde. I had to switch off previews all of media file. -- mouse over an *.avi video file and konqueror crashes https://bugs.launchpad.net/bugs/205884 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 159951] Re: tifm_ms: Unknown symbol tifm_has_ms_pif
I can confirm the same error on Benq R55 Joybook Kernel version 2.6.22-14-generic lscpi output 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express PCI Express Root Port (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 2 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 02) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 02) 01:00.0 VGA compatible controller: nVidia Corporation G72M [GeForce Go 7400] (rev a1) 02:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02) 04:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 10) 05:01.0 CardBus bridge: Texas Instruments PCIxx12 Cardbus Controller 05:01.1 FireWire (IEEE 1394): Texas Instruments PCIxx12 OHCI Compliant IEEE 1394 Host Controller 05:01.2 Mass storage controller: Texas Instruments 5-in-1 Multimedia Card Reader (SD/MMC/MS/MS PRO/xD) 05:01.3 Generic system peripheral [0805]: Texas Instruments PCIxx12 SDA Standard Compliant SD Host Controller -- tifm_ms: Unknown symbol tifm_has_ms_pif https://bugs.launchpad.net/bugs/159951 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 39954] Re: Lucent winmodem driver missing.
Initial bug was reported on 2006-04-18. Now is end of September and I have still the same problem. In restricted modules for i386 kernel version ltmodem driver is compiled, but in k7 and 686 version is not. After all there is no problem with source of ltmodem driver included into Ubuntu kernel if compilation is made by hand. It looks like the only thing to do is append two files to kernel-restricted package for k7 anf 686 version. -- Lucent winmodem driver missing. https://launchpad.net/bugs/39954 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
