[Bug 1950801] Re: Unable to print certain files
This has sucessfully been fixed in Debian with Version 6-3 (https://metadata.ftp- master.debian.org/changelogs//main/b/brlaser/brlaser_6-3_changelog). Can this please be ported to ubuntu as well? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950801 Title: Unable to print certain files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brlaser/+bug/1950801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905441] [NEW] dolphin dataloss on move from ftp to local directory
Public bug reported: I used dolphin to cut & paste files from my android phone (FTP Server Pro) to a local directory (ext4). Some files were copied, but then there was a kde notification saying "move ... failed". Not all files were copied to local, but all files were deleted from the phone. I'd have expected that due to the error, either no files or only successfully copied files would have been removed, so no dataloss would have happened. Description:Ubuntu 20.04.1 LTS Release:20.04 dolphin: Installiert: 4:19.12.3-0ubuntu1 Installationskandidat: 4:19.12.3-0ubuntu1 Versionstabelle: *** 4:19.12.3-0ubuntu1 500 500 http://ftp.tu-ilmenau.de/mirror/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: dolphin 4:19.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Nov 24 18:03:58 2020 SourcePackage: dolphin UpgradeStatus: Upgraded to focal on 2020-10-11 (43 days ago) ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905441 Title: dolphin dataloss on move from ftp to local directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1905441/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874725] [NEW] libpcsc crashes firefox
Public bug reported: My firefox keeps crashing all the time and mozilla crash information says I'm affected by https://bugzilla.mozilla.org/show_bug.cgi?id=1591876. So please update libpcsclite by cherry-picking https://salsa.debian.org/rousseau/PCSC/commit/20385efba2075d4c13acfea43d0abc8c38d8c106 . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libpcsclite1 1.8.23-1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_88_88_generic_65 lkp_Ubuntu_4_15_0_88_88_generic_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: KDE Date: Fri Apr 24 14:56:08 2020 Dependencies: gcc-8-base 8.4.0-1ubuntu1~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.4.0-1ubuntu1~18.04 SourcePackage: pcsc-lite UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874725 Title: libpcsc crashes firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1874725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872162] Re: crash report fail to submit
Though, it is not clear why submitting crashes failes unless re- submitted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872162 Title: crash report fail to submit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872162] Re: crash report fail to submit
Maybe https://salsa.debian.org/rousseau/PCSC/commit/20385efba2075d4c13acfea43d0abc8c38d8c106 can be cherry-picked. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872162 Title: crash report fail to submit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872162] Re: crash report fail to submit
about:crashes -> show -> bugzilla lists mozilla bug 1591876 select() crashes in libpcslite. https://bugzilla.mozilla.org/show_bug.cgi?id=1591876 As http://changelogs.ubuntu.com/changelogs/pool/main/p/pcsc-lite/pcsc- lite_1.8.23-1/changelog is older than the fix reported in the mozilla bugtracker, ubuntu 18.04 likely is still affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872162 Title: crash report fail to submit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872162] Re: crash report fail to submit
Yes, that was working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872162 Title: crash report fail to submit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872162] Re: crash report fail to submit
Thanks ** Bug watch added: Mozilla Bugzilla #1591876 https://bugzilla.mozilla.org/show_bug.cgi?id=1591876 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872162 Title: crash report fail to submit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872162] [NEW] crash report fail to submit
Public bug reported: Since 2020-03-19, firefox crashed about 17 times (it did not crash 1,5 years before). Though, all crash reports failed to submit. My firefox crash report submit.log reads: [Mo 17 Dez 2018 00:14:42 CET] Crash report submitted successfully [Do 19 Mär 2020 00:06:24 CET] Crash report submission failed: Couldn't connect to server [Sa 21 Mär 2020 15:14:19 CET] Crash report submission failed: Couldn't connect to server [Di 24 Mär 2020 23:22:51 CET] Crash report submission failed: Couldn't connect to server [Mi 25 Mär 2020 14:22:41 CET] Crash report submission failed: Couldn't connect to server [Do 26 Mär 2020 17:40:46 CET] Crash report submission failed: Couldn't connect to server [Sa 28 Mär 2020 10:59:32 CET] Crash report submission failed: Couldn't connect to server [Mo 30 Mär 2020 01:03:56 CEST] Crash report submission failed: Couldn't connect to server [Mi 01 Apr 2020 16:01:11 CEST] Crash report submission failed: Couldn't connect to server [Do 02 Apr 2020 20:39:29 CEST] Crash report submission failed: Couldn't connect to server [Fr 03 Apr 2020 21:07:53 CEST] Crash report submission failed: Couldn't connect to server [So 05 Apr 2020 22:38:08 CEST] Crash report submission failed: Couldn't connect to server [Di 07 Apr 2020 21:40:43 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 13:05:39 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 20:16:28 CEST] Crash report submission failed: Couldn't connect to server [Mi 08 Apr 2020 22:27:58 CEST] Crash report submission failed: Couldn't connect to server [Do 09 Apr 2020 23:36:31 CEST] Crash report submission failed: Couldn't connect to server [Fr 10 Apr 2020 20:07:48 CEST] Crash report submission failed: Couldn't connect to server ** Affects: firefox (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/1872162 Title: crash report fail to submit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1872162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820913] Re: func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible; expected minor version=2; real minor version=2; expected subm
Workaround: disable OpenCL software emulation and Java Runtime in Options. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820913 Title: func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820913] [NEW] func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible; expected minor version=2; real minor version=2; expected su
Public bug reported: I'm starting libreoffice with an docx document and it immediately crashes outputting the following text on console. The file opens fine on a different computer with an older libreoffice version. func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26 This as been fixed upstream at https://bugs.documentfoundation.org/show_bug.cgi?id=118373 and reported also by other users at https://forum.ubuntuusers.de/topic/upgrade- von-16-04-nach-18-04-libreoffice-oeffn/ Description:Ubuntu 18.04.2 LTS Release:18.04 libreoffice: Installiert: 1:6.0.7-0ubuntu0.18.04.2 Installationskandidat: 1:6.0.7-0ubuntu0.18.04.2 Versionstabelle: *** 1:6.0.7-0ubuntu0.18.04.2 700 700 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 700 700 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820913 Title: func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1820913/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808705] [NEW] printing on remote printer from GTK applications fails using duplex
Public bug reported: Steps to reproduce: 1. add remote ipp printer (remote is running ubuntu cups) using system-config-printer -> shows printer type "remote printer", printers setting in system-config-printer shows duplex, paper and other options from remote ppd, there is no local ppd in /etc/cups/ppd/ for this printer and no MakeModel in printers.conf. 2. try to print from firefox -> Duplex, Paper Type and other options are greyed out and shown as "not available" Workaround: 1. copy ppd from remote cups server, though this may not always work (filters not available locally or remote cups not accepted binary blob already processed by cupsFilter) 2. use generic ipp profile (does not support all target features) 3. use driverless to generate ppd (may not catch all target features) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups-filters 1.20.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Sun Dec 16 13:36:17 2018 InstallationDate: Installed on 2015-09-14 (1189 days ago) InstallationMedia: Lubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) Lpstat: device for HLL2300D: ipp://172.16.1.20:631/printers/HLL2300D device for Kyocera-Mita-FS-1020D: socket://172.16.1.21 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 006: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox Papersize: a4 PpdFiles: Kyocera-Mita-FS-1020D: Kyocera Mita FS-1020D HLL2300D: Brother HL-L2300D for CUPS (remote) ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=c34300f7-d295-40ce-8c33-586987f5f41f ro quiet splash SourcePackage: cups-filters UpgradeStatus: Upgraded to bionic on 2018-09-09 (97 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808705 Title: printing on remote printer from GTK applications fails using duplex To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1808705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804048] Re: virtualbox crashes when enabling vrde
** Patch added: "VBoxVNC.fix.diff" https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1804048/+attachment/5214288/+files/VBoxVNC.fix.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804048 Title: virtualbox crashes when enabling vrde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1804048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804048] [NEW] virtualbox crashes when enabling vrde
Public bug reported: > VBoxManage controlvm 59d1f359-3d9c-4d5d-8404-266f9b5cff22 vrde on dmesg: [ 48.504536] vboxdrv: loading out-of-tree module taints kernel. [ 48.504692] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel [ 48.510697] vboxdrv: Found 8 processor cores [ 48.528266] vboxdrv: TSC mode is Invariant, tentative frequency 3411479167 Hz [ 48.528268] vboxdrv: Successfully loaded version 5.2.10_Ubuntu (interface 0x00290001) [ 48.533241] VBoxNetFlt: Successfully started. [ 48.537052] VBoxNetAdp: Successfully started. [ 48.540636] VBoxPciLinuxInit [ 48.542513] vboxpci: IOMMU not found (not registered) [ 68.688010] vboxdrv: VMMR0.r0 [ 69.082086] vboxdrv: VBoxDDR0.r0 [ 69.194586] vboxdrv: VBoxEhciR0.r0 [ 360.899738] EMT-3[2493]: segfault at 16952 ip 7f73b89fcf77 sp 7f745abfaa08 error 4 in VBoxVNC.so[7f73b89fb000+4000] -> VBox crashed. Reported Upstream 20 Months ago: https://www.virtualbox.org/ticket/16603 With patch provided. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virtualbox 5.2.10-dfsg-6ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Nov 19 20:19:50 2018 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: virtualbox UpgradeStatus: Upgraded to bionic on 2018-09-08 (72 days ago) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804048 Title: virtualbox crashes when enabling vrde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1804048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804048] Re: virtualbox crashes when enabling vrde
Solution already proposed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804048 Title: virtualbox crashes when enabling vrde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1804048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791513] Re: system hang after resume from standby with i915 in bionic
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791513/+attachment/5186751/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791513 Title: system hang after resume from standby with i915 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791513/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791513] [NEW] system hang after resume from standby with i915 in bionic
Public bug reported: I've upgraded my i7-2600 system (cpu with integrated i915) from ubuntu 16.04 x86_64 to 18.04.1 x86_64 using do-release-upgrade. It works fine except hanging after resume from standby. The system does to standby (suspend to ram) when idle automatically. When it text console, it resumes fine from pm-suspend, but after switching to graphics the system hangs (magic sysrq does not work either). The problem occurs with 4.15.0-33-generic and is also present with mainline 4.18.7. kern.log ends with: "kernel: PM: suspend entry (deep)". When resuming into text console first, I get kernel: [ 117.272524] PM: suspend entry (deep) kernel: [ 117.272526] PM: Syncing filesystems ... done. kernel: [ 117.354945] Freezing user space processes ... (elapsed 0.001 seconds) done. kernel: [ 117.356708] OOM killer disabled. kernel: [ 117.356709] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. kernel: [ 117.357920] Suspending console(s) (use no_console_suspend to debug) kernel: [ 117.359239] serial 00:05: disabled kernel: [ 117.359734] parport_pc 00:02: disabled kernel: [ 117.388004] sd 3:0:0:0: [sdb] Synchronizing SCSI cache kernel: [ 117.388119] sd 3:0:0:0: [sdb] Stopping disk kernel: [ 117.395014] sd 2:0:0:0: [sda] Synchronizing SCSI cache kernel: [ 117.395123] sd 2:0:0:0: [sda] Stopping disk kernel: [ 118.008264] ACPI: Preparing to enter system sleep state S3 kernel: [ 118.009459] PM: Saving platform NVS memory kernel: [ 118.009851] Disabling non-boot CPUs ... kernel: [ 118.025074] smpboot: CPU 1 is now offline kernel: [ 118.049113] smpboot: CPU 2 is now offline kernel: [ 118.073695] smpboot: CPU 3 is now offline kernel: [ 118.096142] IRQ 16: no longer affine to CPU4 kernel: [ 118.097170] smpboot: CPU 4 is now offline kernel: [ 118.120153] IRQ 25: no longer affine to CPU5 kernel: [ 118.120163] IRQ 30: no longer affine to CPU5 kernel: [ 118.120168] IRQ 31: no longer affine to CPU5 kernel: [ 118.120174] IRQ 33: no longer affine to CPU5 kernel: [ 118.120182] IRQ 38: no longer affine to CPU5 kernel: [ 118.121192] smpboot: CPU 5 is now offline kernel: [ 118.144160] IRQ 23: no longer affine to CPU6 kernel: [ 118.144165] IRQ 27: no longer affine to CPU6 kernel: [ 118.144173] IRQ 32: no longer affine to CPU6 kernel: [ 118.144186] IRQ 37: no longer affine to CPU6 kernel: [ 118.145194] smpboot: CPU 6 is now offline kernel: [ 118.169244] smpboot: CPU 7 is now offline kernel: [ 118.170914] ACPI: Low-level resume complete kernel: [ 118.170954] PM: Restoring platform NVS memory kernel: [ 118.172220] Enabling non-boot CPUs ... kernel: [ 118.172262] x86: Booting SMP configuration: kernel: [ 118.172262] smpboot: Booting Node 0 Processor 1 APIC 0x2 kernel: [ 118.175214] cache: parent cpu1 should not be sleeping kernel: [ 118.175439] CPU1 is up kernel: [ 118.175481] smpboot: Booting Node 0 Processor 2 APIC 0x4 kernel: [ 118.178697] cache: parent cpu2 should not be sleeping kernel: [ 118.178941] CPU2 is up kernel: [ 118.178988] smpboot: Booting Node 0 Processor 3 APIC 0x6 kernel: [ 118.182312] cache: parent cpu3 should not be sleeping kernel: [ 118.182576] CPU3 is up kernel: [ 118.182623] smpboot: Booting Node 0 Processor 4 APIC 0x1 kernel: [ 118.185397] cache: parent cpu4 should not be sleeping kernel: [ 118.185713] CPU4 is up kernel: [ 118.185762] smpboot: Booting Node 0 Processor 5 APIC 0x3 kernel: [ 118.188483] cache: parent cpu5 should not be sleeping kernel: [ 118.188788] CPU5 is up kernel: [ 118.188823] smpboot: Booting Node 0 Processor 6 APIC 0x5 kernel: [ 118.191562] cache: parent cpu6 should not be sleeping kernel: [ 118.191888] CPU6 is up kernel: [ 118.191926] smpboot: Booting Node 0 Processor 7 APIC 0x7 kernel: [ 118.194646] cache: parent cpu7 should not be sleeping kernel: [ 118.194994] CPU7 is up kernel: [ 118.202014] ACPI: Waking up from system sleep state S3 kernel: [ 118.222689] usb usb3: root hub lost power or was reset kernel: [ 118.222692] usb usb4: root hub lost power or was reset kernel: [ 118.223745] parport_pc 00:02: activated kernel: [ 118.225587] sd 2:0:0:0: [sda] Starting disk kernel: [ 118.225622] sd 3:0:0:0: [sdb] Starting disk kernel: [ 118.226036] serial 00:05: activated kernel: [ 118.32] ata7.01: ACPI cmd ef/03:46:00:00:00:b0 (SET FEATURES) filtered out kernel: [ 118.392639] r8169 :05:00.0 eth0: link down kernel: [ 118.393320] ata7.00: ACPI cmd ef/03:46:00:00:00:a0 (SET FEATURES) filtered out kernel: [ 118.398576] ata7.00: configured for UDMA/33 kernel: [ 118.403760] ata7.01: configured for UDMA/66 kernel: [ 118.560972] ata5: SATA link up 1.5 Gbps (SStatus 113 SControl 300) kernel: [ 118.568140] ata5.00: configured for UDMA/100 kernel: [ 118.726420] usb 3-1: reset low-speed USB device number 2 using xhci_hcd kernel: [ 119.210956] usb 3-2: reset high-speed USB device number 3 using xhci_hcd kernel: [ 119.727434] usb 3-2.4: reset high-speed USB device number 5 using xhci_hcd
[Bug 1744391] Re: eeepc display corruption with kernel 4.13
** Attachment added: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+attachment/5039754/+files/lspci.txt ** Description changed: When booting kernel 4.13, the display corrupts after grub boot menu. The problem persists with mainline kernel 4.14.13 but does not occur with kernel 4.10 or 4.4. I'm running Xenial i386 on EEEPC. - The kernel log shows "plane B assertion failure, should be off on pipe B - but is still active". See attached dmesg excerpt. + The kernel log shows "plane B assertion failure, should be off on pipe B but is still active". See attached dmesg excerpt. + Jan 15 20:23:39 skarabaeus kernel: [3.778791] WARNING: CPU: 0 PID: 144 at /build/linux-hwe-aMp2XS/linux-hwe-4.13.0/drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x11e/0x140 [i915] - The bug is widespread: - https://bugs.freedesktop.org/show_bug.cgi?id=102929 - https://bugzilla.redhat.com/show_bug.cgi?id=1498725 + + The bug is widespread: https://bugs.freedesktop.org/show_bug.cgi?id=102929 https://bugzilla.redhat.com/show_bug.cgi?id=1498725 It has a patch pending that others have confirmed working. Maybe this patch should be ported to ubuntu. - Description: Ubuntu 16.04.3 LTS Release: 16.04 ** Description changed: When booting kernel 4.13, the display corrupts after grub boot menu. The problem persists with mainline kernel 4.14.13 but does not occur with kernel 4.10 or 4.4. I'm running Xenial i386 on EEEPC. The kernel log shows "plane B assertion failure, should be off on pipe B but is still active". See attached dmesg excerpt. Jan 15 20:23:39 skarabaeus kernel: [3.778791] WARNING: CPU: 0 PID: 144 at /build/linux-hwe-aMp2XS/linux-hwe-4.13.0/drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x11e/0x140 [i915] - - The bug is widespread: https://bugs.freedesktop.org/show_bug.cgi?id=102929 https://bugzilla.redhat.com/show_bug.cgi?id=1498725 + The bug is widespread: + https://bugs.freedesktop.org/show_bug.cgi?id=102929 + https://bugzilla.redhat.com/show_bug.cgi?id=1498725 It has a patch pending that others have confirmed working. Maybe this - patch should be ported to ubuntu. + patch should be ported to ubuntu. See both referenced issues. Description: Ubuntu 16.04.3 LTS Release: 16.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744391 Title: eeepc display corruption with kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744391] Re: eeepc display corruption with kernel 4.13
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+attachment/5039752/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744391 Title: eeepc display corruption with kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744391] [NEW] eeepc display corruption with kernel 4.13
Public bug reported: When booting kernel 4.13, the display corrupts after grub boot menu. The problem persists with mainline kernel 4.14.13 but does not occur with kernel 4.10 or 4.4. I'm running Xenial i386 on EEEPC. The kernel log shows "plane B assertion failure, should be off on pipe B but is still active". See attached dmesg excerpt. Jan 15 20:23:39 skarabaeus kernel: [3.778791] WARNING: CPU: 0 PID: 144 at /build/linux-hwe-aMp2XS/linux-hwe-4.13.0/drivers/gpu/drm/i915/intel_display.c:1252 assert_planes_disabled+0x11e/0x140 [i915] The bug is widespread: https://bugs.freedesktop.org/show_bug.cgi?id=102929 https://bugzilla.redhat.com/show_bug.cgi?id=1498725 It has a patch pending that others have confirmed working. Maybe this patch should be ported to ubuntu. See both referenced issues. Description:Ubuntu 16.04.3 LTS Release:16.04 ** Affects: linux-meta-hwe (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/1744391 Title: eeepc display corruption with kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744391] Re: eeepc display corruption with kernel 4.13
** Attachment added: "hwe-version.txt" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+attachment/5039753/+files/hwe-version.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744391 Title: eeepc display corruption with kernel 4.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1744391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721854] [NEW] failed to install grub in installation
Public bug reported: when I install Ubuntu installation goes well until grub failed and "sorry we can't install this system "message showed ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CasperVersion: 1.376.2 Date: Fri Oct 6 20:54:07 2017 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721854 Title: failed to install grub in installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1721854/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502593] Re: bwm-ng: Changing input method causes program to quit
That fix has not yet shown up in xenial, so that bug is still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502593 Title: bwm-ng: Changing input method causes program to quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719156] [NEW] bwm-ng: Changing input method causes program to quit
Public bug reported: Same as https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593, but specific for xenial release. ** Affects: bwm-ng (Ubuntu) Importance: Undecided Status: New ** Description changed: Same as https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593, - bug specific for xenial release. + but specific for xenial release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719156 Title: bwm-ng: Changing input method causes program to quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1719156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with any kernel above 3.17
Well I figured out that this issue is present in any laptop I was able to test, I tried with several laptops with new and not so new hardware and it is always the same. Asus, MSI, Lenovo, HP and Compaq, Dell, Toshiba, Intel Classmate Netbooks have the same problem after kernel 3.17. Is there anything else that I could try? Thnx -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with any kernel above 3.17 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with any kernel above 3.17
to help you guys, Thanks in advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with any kernel above 3.17 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with any kernel above 3.17
I've changed the subject to be more accurate with the first kernel version affected by this issue. Please let me know any other thing you need, I will be pleased t ** Summary changed: - Cannot get lowest brightness with kernel 4.4.0-53-generic + Cannot get lowest brightness with any kernel above 3.17 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with any kernel above 3.17 To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
Ok, I can confirm that the latest mainline kernel does not fix this bug. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
I can confirm that the issue can be experienced also in any ClassmatePC by Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
Yes, It would be possible for me, but these days I'm on holiday and I'm in a place with very poor Internet connection, so I think I'm gonna be able to test the last kernel in a couple of days. Thank you for your time -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861620/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861619/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861621/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861618/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861617/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861616/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861609/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861615/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861614/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861612/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861613/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861611/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
apport information ** Description changed: - I have been using kernel 3.16/3.19 in my Dell Laptop for a long time - with Linux Mint 17 and previous versions and the problem here had never + I have been using kernel 3.16 in my Dell Laptop for a long time with + Linux Mint 17 and previous versions and the problem here had never happened until LM18. Very often I set the lowest possible brightness, for example at night, or while I am flying for many hours. Using values from 0 to 4882 I used to run this command: - # ie: Set lowest possible backlight brightness + # ie: Set lowest possible backlight brightness echo 0 > /sys/class/backlight/intel_backlight/brightnes I have always used intel_backlight instead of dell_backlight because it gives much more steps. Well now with kernel 4.4.0-53-generic it actually decreases the brightness but at night it is still very high even at 0 compared to the brightness levels I used to get with the same command. In fact, using a value of 0 with older kernels, the backlight is turned off. Just for testing, I have booted my laptop with Debian Live kernel 3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That is how I realized that the problem was the kernel. Does anyone know if with newer kernels > 3.19 this is a well-known and tolerated behavior? Maybe the kernel code for intel_backlight was modified and ended up with this problem... Some system information: System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0) -Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 18.1 Serena + Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 18.1 Serena Machine: System: Dell product: Inspiron 5520 v: A14 Bios: Dell v: A14 date: 05/13/2013 CPU: Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB - Graphics: Card: Intel 3rd Gen Core processor Graphics Controller -Display Server: X.org 1.18.4 driver: intel + Graphics: Card: Intel 3rd Gen Core processor Graphics Controller + Display Server: X.org 1.18.4 driver: intel $ ls /sys/class/backlight/ dell_backlight intel_backlight Also I always use the acpi_backlight=vendor kernel parameter and I can confirm that by changing its value, the problem persists. Thanks for your time, Frk. P.S. I have also asked about this issue without luck here => https://goo.gl/TVzH7z ** Tags added: apport-collected serena ** Description changed: I have been using kernel 3.16 in my Dell Laptop for a long time with Linux Mint 17 and previous versions and the problem here had never happened until LM18. Very often I set the lowest possible brightness, for example at night, or while I am flying for many hours. Using values from 0 to 4882 I used to run this command: # ie: Set lowest possible backlight brightness echo 0 > /sys/class/backlight/intel_backlight/brightnes I have always used intel_backlight instead of dell_backlight because it gives much more steps. Well now with kernel 4.4.0-53-generic it actually decreases the brightness but at night it is still very high even at 0 compared to the brightness levels I used to get with the same command. In fact, using a value of 0 with older kernels, the backlight is turned off. Just for testing, I have booted my laptop with Debian Live kernel 3.16.0-4-amd64 and it works perfectly. Nevertheless I was able to reproduce the issue on newer ubuntu releases and Fedora 25.3.1. That is how I realized that the problem was the kernel. Does anyone know if with newer kernels > 3.19 this is a well-known and tolerated behavior? Maybe the kernel code for intel_backlight was modified and ended up with this problem... Some system information: System:Kernel: 4.4.0-53-generic x86_64 (64 bit gcc: 5.4.0) Desktop: Cinnamon 3.2.7 (Gtk 3.18.9-1ubuntu3.2) Distro: Linux Mint 18.1 Serena Machine: System: Dell product: Inspiron 5520 v: A14 Bios: Dell v: A14 date: 05/13/2013 CPU: Dual core Intel Core i5-3210M (-HT-MCP-) cache: 3072 KB Graphics: Card: Intel 3rd Gen Core processor Graphics Controller Display Server: X.org 1.18.4 driver: intel $ ls /sys/class/backlight/ dell_backlight intel_backlight Also I always use the acpi_backlight=vendor kernel parameter and I can confirm that by changing its value, the problem persists. Thanks for your time, Frk. - P.S. I have also asked about this issue without luck here => - https://goo.gl/TVzH7z + P.S. I have also asked about this issue without luck here => https://goo.gl/TVzH7z + --- + ApportVersion: 2.20.1-0ubuntu2.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: betops 6791 F pulseaudio + CurrentDesktop: X-Cinnamon +
[Bug 1682331] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861608/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1682331/+attachment/4861610/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
To my surprise I have found that the last kernel working fine from mainline is: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.43/ and the first kernel with the issue is 3.17 RC1 http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc1-utopic/ I hope this help kernel coders to find the solution. I do not know what else I could do. Just ask me whatever you need, I will help as much as I can. Tank you very much!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
Ok, I'm testing one by one and as soon as I get results I'm posting it here. 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/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682331] Re: Cannot get lowest brightness with kernel 4.4.0-53-generic
** Also affects: ubuntu Importance: Undecided Status: New ** Also affects: fedora 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/1682331 Title: Cannot get lowest brightness with kernel 4.4.0-53-generic To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1682331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652544] [NEW] Kernel BUG in rtl8723be
Public bug reported: 1. suspend 2. resume 3. wifi is now unusable 4. rmmod rtl8723be 5. find kernel BUG in dmesg ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mbr1916 F pulseaudio CurrentDesktop: Unity Date: Mon Dec 26 00:53:04 2016 HibernationDevice: RESUME=UUID=5ce2d2d7-2115-465a-bd19-5ae7b194fb0b InstallationDate: Installed on 2016-03-25 (275 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b49f Chicony Electronics Co., Ltd Bus 001 Device 002: ID 174f:1169 Syntek Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MJ ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed root=UUID=100567cc-c832-47cd-89e2-42a875689e44 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: CCCN15WW(V2.01) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 100-15IBY dmi.modalias: dmi:bvnLENOVO:bvrCCCN15WW(V2.01):bd09/03/2015:svnLENOVO:pn80MJ:pvrLenovoideapad100-15IBY:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBY: dmi.product.name: 80MJ dmi.product.version: Lenovo ideapad 100-15IBY dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652544 Title: Kernel BUG in rtl8723be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1652544] Re: Kernel BUG in rtl8723be
** Attachment added: "dmesg log when BUG was hit" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652544/+attachment/4796388/+files/dmesg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652544 Title: Kernel BUG in rtl8723be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651984] [NEW] kio ftp uses absolute paths with SIZE command
Public bug reported: kio-ftp should use relative paths with SIZE command whenever possible. This was already fixed 2014 in KDE 4.14.2, but is broken in current ubuntu kde. https://cgit.kde.org/kdelibs.git/commit/?id=d6453435f0d475e16b2512782b9b3e40bb603da1 Wireshark FTP Trace: 220 SwiFTP 2.11.3 ready USER ftp 331 Send password PASS *secret* 230 Access granted SYST 215 UNIX Type: L8 PWD 257 "/" cwd /DCIM/Camera/20160729_102840_HDR.jpg 550 Can't CWD to invalid directory cwd /DCIM/Camera 250 CWD successful TYPE I 200 Binary type set PASV 227 Entering Passive Mode (172,16,3,20,210,32). list 20160729_102840_HDR.jpg 150 Opening BINARY mode data connection for file list 226 Data transmission OK SIZE /DCIM/Camera/20160729_102840_HDR.jpg 550 No directory traversal allowed in SIZE param cwd /DCIM/Camera/20160729_102840_HDR.jpg 550 Can't CWD to invalid directory PASV 227 Entering Passive Mode (172,16,3,20,169,255). retr /DCIM/Camera/20160729_102840_HDR.jpg 150 Sending file 226 Transmission finished ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kio 5.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 22 10:17:55 2016 SourcePackage: kio UpgradeStatus: Upgraded to xenial on 2016-04-22 (243 days ago) ** Affects: kio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651984 Title: kio ftp uses absolute paths with SIZE command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kio/+bug/1651984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 275304] Re: run as different user fails (wrong ownership of .Xauthority and /tmp/libgksu-xxx)
Still present with xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/275304 Title: run as different user fails (wrong ownership of .Xauthority and /tmp /libgksu-xxx) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/275304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502593] Re: bwm-ng: Changing input method causes program to quit
What is needed to get this fix into xenial? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502593 Title: bwm-ng: Changing input method causes program to quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574544] Re: Light-locker-settings crash on startup
** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574544 Title: Light-locker-settings crash on startup To manage notifications about this bug go to: https://bugs.launchpad.net/light-locker-settings/+bug/1574544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502593] Re: bwm-ng: Changing input method causes program to quit
** Tags added: patch patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1502593 Title: bwm-ng: Changing input method causes program to quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507764] Re: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout
After upgrading to xenial, by laptop is crashing every few hours or so. dmesg says metacity crashed, and then I get logged off with all applications closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507764 Title: metacity crashed with signal 5 in _XEventsQueued() ; forcing gnome session to logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1507764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
Thanks for driving this forward. You argue from > So let us make one thing clear, IMHO if something overloads your machine with > disk I/O it has to stall it. This is a bit tricky, because overload means that the machine will be able not complete all task in the time given, i.e. tasks will accumulate until the resources are exhausted. Though, we usually do not have this situation on desktop machines. There we have tasks to do and want them to complete as fast as possible, thought some tasks may take longer than others. For example, copying a 5 GB DVD disk will take some minutes or so, but refreshing the browser window or switching windows should never. Overlay here would mean the user will turn of the machine and by a windows licence. So this bug is mostly about having too big delays in applications using only a small bit of the available resources (like when switching back to a libreoffice window) when some other applications (like background file indexing) are asking for the remaining disk io resource capacities. > Code improves to mitigate effects but can never be perfect for *ALL* users at once (especially in the default config) I do not agree. Desktop responsiveness was achieved with older ubuntu versions on the given hw and is achieved with other operating systems (windows) on a broad range of hardware. I believe desktop responsiveness is something sufficiently specific a cpu and io scheduler can be tuned to. Using cgroups and alike might help, but should be configured by Ubuntu by default if necessary. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/131094 Title: Heavy Disk I/O harms desktop responsiveness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/131094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1502593] [NEW] bwm-ng: Changing input method causes program to quit
Public bug reported: When changing input method the program exists with a non-zero exit status (1) with the message: libstatgrab error! I'm running ii bwm-ng0.6-3.1ubuntu2amd64 small and simple console-based bandwidth monitor on ubuntu trusty. This is the same as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746014 Upstream fixed this with https://github.com/vgropp/bwm-ng/commit/20c51f46720dbf329e0ec46654d55b2e4d696a8a which would also apply to the ubuntu package. ** Affects: bwm-ng (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/1502593 Title: bwm-ng: Changing input method causes program to quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bwm-ng/+bug/1502593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131094] Re: Heavy Disk I/O harms desktop responsiveness
@Christopher: This is not incomplete. Thanks. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/131094 Title: Heavy Disk I/O harms desktop responsiveness To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/131094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1250196] Re: sane plustek backend not working on USB 3 root hub
Running trusty with N670U (LiDE 20) the issues were resolved using https://launchpad.net/~rolfbensch/+archive/ubuntu/sane- git/+build/7834143 . I'm also missing updated packages in default ubuntu repositories. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1250196 Title: sane plustek backend not working on USB 3 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268771] Re: NVIDIA Prime fails with Linux 3.13
anyone looking for a solution might also want to give https://devtalk.nvidia.com/default/topic/684651/linux/ux32vd-quot- failed-to-copy-vbios-to-system-memory-quot-yet-again/ a try. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268771 Title: NVIDIA Prime fails with Linux 3.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
What I can reproduce on another machine is: 1. create a file (ods) with default date settings 2. close file 3. change date setting 4. open file and find a different date displayed. I don't understand why this is happening, because the content.xml says table:table-cell office:value-type=date office:date-value=2014-01-01 calcext:value-type=date text:p01.01.14/text:p /table:table-cell which is no relative date. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: [Upstream] Dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
Further, I would expect that change to only affect ambiguous dates (in file formats that do not use four digit years, for example) - because what is the point in changing a date based on a program setting? Or maybe when actually doing some calculation, because this setting is in the calculate section. Further, one can only change this setting with a calc file open (otherwise the menu is missing) - so it will always affect a file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: [Upstream] Dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
1/ How do you change date setting if the file is closed ? I created (opened) a new file (not saved) and changed it then. The change shows up in user/registrymodifications.xcu . 2/ where is random ? All changes are made by you, Calc does only what you asked him to do. I originally did what I wrote in steps to reproduce. Originally, I first had a document created on another computer that showed up with wrong dates. Then I found that even documents created locally showed wrong dates. After changing the setting mentioned back to defaults, the issue was gone. But it could be reproduced by the steps mentioned in steps to reproduce. So I thought this was an unacceptable issue with libreoffice. I'm now facing difficulties to reproduce this even on the machine that originally exhibited this behaviour (which does not always even have internet access). So I don't know how to debug this further. Regardless of the original issue, I find it very strange as a user that changing that very setting changes the static! document content. I think this is not easy to see as a user (when going through menu) and does not only affect calculations as one could expect from menu structure. 3/ the origin date is saved in the content.xml if it is not the standard origin date (1899.12.30). Open such a content.xml and search for null- date. thanks for pointing that out. 4/ when reading a file Calc converts dates to numbers (decimal) of days from the null-date. It converts back to dates when formatting and saving. I think it would improve user experience when changing that setting would not alter static (non-calculated) content. Set status to NEEDINFO. Please set it back to UNCONFIRMED once you have provided requested informations. Thank you for your understanding. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: [Upstream] Dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
Created attachment 106048 screencast showing the change of the date when changing the setting This is on yet another machine, running ubuntu mint 16 with a fresh profile. It shows that the displayed date changes too when changing the setting. it is libreoffice 4.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: [Upstream] Dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
ok, please give me some time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: [Upstream] Dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
Created attachment 106050 screencast again showing libreoffice 4.3 this is on ubuntu mint again, the old libreoffice profile has been removed in advance, and a new libreoffice 4.3 version from libreoffice.org installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: [Upstream] Dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 978742] Re: notification-daemon crashed with signal 5 in g_return_if_fail_warning()
Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636323) has a patch available. ** Bug watch added: Debian Bug tracker #636323 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636323 ** Also affects: notification-daemon (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636323 Importance: Unknown Status: Unknown ** Tags added: patch patch-accepted-debian -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/978742 Title: notification-daemon crashed with signal 5 in g_return_if_fail_warning() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notification-daemon/+bug/978742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1362313] [NEW] a2dp bluetooth music playback broken after bluetooth device reconnect
Public bug reported: What happens? 1. connct a2dp device 2. start playback 3. reconnect a2dp device from remote 4. ubuntu reports device is connected 5. a2dp device does not show up in pulseaudio nor does music playback work (via a2dp device). sometimes there are timeout error messages in kde. 6. try to reconnect from ubuntu, restart bluetooth daemon, restart pulseaudio daemon. it all does not help. 7. what does help is restarting 1. dbus 2. bluetooth and 3. pulseaudio then connect the device (if not already auto-connected) After step 3, there is the following error message in syslog (no other errors in syslog or dmesg): pulseaudio[7812]: [bluetooth] bluetooth-util.c: Failed to release transport /org/bluez/7791/hci0/dev_C8_84_47_10_24_A2/fd2: Method Release with signature s on interface org.bluez.MediaTransport doesn't exist What I expected to happen? After the device reconnect, the music playback switches playback back to the bluetooth device. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bluetooth 4.101-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 27 21:41:34 2014 InterestingModules: rfcomm bnep btusb bluetooth MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-32-generic root=/dev/mapper/linux64-root64 ro nomdmonddf nomdmonisw nomdmonddf nomdmonisw SourcePackage: bluez UpgradeStatus: Upgraded to trusty on 2014-06-18 (70 days ago) dmi.bios.date: 12/06/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: B85 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd12/06/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB85Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 00:02:72:CC:E6:D5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:100536 acl:18 sco:0 events:14179 errors:0 TX bytes:24059553 acl:28186 sco:0 commands:77 errors:0 syslog: Aug 27 20:46:20 charlie bluetoothd[1538]: /org/bluez/1538/hci0/dev_C8_84_47_10_24_A2/fd0: fd(25) ready ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1362313 Title: a2dp bluetooth music playback broken after bluetooth device reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1362313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546]
It happened with a specific one copied from another computer but I was able to reproduce this creating a new one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1345546] [NEW] dates in cell change randomly on load
Public bug reported: Problem description: Steps to reproduce: 0. This is on Ubuntu x86_64 in german local, I did not test others. 1. Set Settings - Libreoffice Calc - Berechnen (Calculation?) - Date = 1.1.1904 2. Create new spreadsheet 3. Enter 2.6.2014 in the cell (here: german date format, maybe 2014-06-02 in English) 4. Save file 5. Close file 6. Reopen file 7. Display file 8. save the file Current behavior: After step 4, 2014-06-02 is saved in content.xml in the ods file: table:table-cell office:value-type=date office:date-value=2014-06-02 calcext:value-type=date text:p02.06.14/text:p /table:table-cell But it step 7, it is display as 1.6.2010 (that is 2010-06-01) . After saving in step 8, content.xml contains: table:table-cell office:value-type=date office:date-value=2010-06-01 calcext:value-type=date text:p01.06.10/text:p /table:table-cell The current mode of operation breaks file display and corrupts the original file! Expected behavior: The date should not change, neither while displaying nor when saving the file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.4-0ubuntu2 Uname: Linux 3.15.0-031500rc7-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jul 20 12:58:26 2014 SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-06-18 (31 days ago) ** Affects: df-libreoffice Importance: Unknown Status: Unknown ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Bug watch added: freedesktop.org Bugzilla #81560 https://bugs.freedesktop.org/show_bug.cgi?id=81560 ** Also affects: df-libreoffice via https://bugs.freedesktop.org/show_bug.cgi?id=81560 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: dates in cell change randomly on load To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1304143] Re: ImportError: cannot import name 'ki18n' when launching gdebi-kde
gdebi_0.9.5.3ubuntu2_all.deb gdebi-core_0.9.5.3ubuntu2_all.deb gdebi- kde_0.9.5.3ubuntu2_all.deb from trusty-proposed fixed the issue for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1304143 Title: ImportError: cannot import name 'ki18n' when launching gdebi-kde To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1304143/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307682] Re: samba full_audit reports wrong username when using force user
** Patch added: 0001-Fix-bug-8882-Broken-processing-of-U-with-vfs_full_au.patch https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+attachment/4132495/+files/0001-Fix-bug-8882-Broken-processing-of-U-with-vfs_full_au.patch ** Tags added: patch patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307682 Title: samba full_audit reports wrong username when using force user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+subscriptions -- 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 1307682] Re: samba full_audit reports wrong username when using force user
** Patch added: 0001-Fix-bug-8882-Broken-processing-of-U-with-vfs_full_au.patch https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+attachment/4132495/+files/0001-Fix-bug-8882-Broken-processing-of-U-with-vfs_full_au.patch ** Tags added: patch patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307682 Title: samba full_audit reports wrong username when using force user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310055] Re: rt2x00 driver doesn't load for 57c:8501 (AVM Fritz Stick Nv2)
** Attachment added: 02-rt2800usb-fix-hang-during-firm https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310055/+attachment/4123785/+files/02-rt2800usb-fix-hang-during-firm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310055 Title: rt2x00 driver doesn't load for 57c:8501 (AVM Fritz Stick Nv2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310055] Re: rt2x00 driver doesn't load for 57c:8501 (AVM Fritz Stick Nv2)
** Attachment added: 01-rt2800usb-fix-efuse-detection https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310055/+attachment/4123784/+files/01-rt2800usb-fix-efuse-detection -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310055 Title: rt2x00 driver doesn't load for 57c:8501 (AVM Fritz Stick Nv2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1310055] Re: rt2x00 driver doesn't load for 57c:8501 (AVM Fritz Stick Nv2)
Please find attached two patches on top of 3.15-rc7 (vanilla kernel) that makes my 57c:8501 (AVM Fritz Stick N v2 - B) device work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1310055 Title: rt2x00 driver doesn't load for 57c:8501 (AVM Fritz Stick Nv2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1310055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1307682] [NEW] samba full_audit reports wrong username when using force user
Public bug reported: When using force user in combination with full_audit, the %U audit marco get replaced with the wrong (forced) username. This has been fixed upstream two years ago, but is not yet in precise. https://bugzilla.samba.org/show_bug.cgi?id=8882 You be great to apply this to precise as well. https://attachments.samba.org/attachment.cgi?id=7476 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: samba 2:3.6.3-2ubuntu2.10 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Apr 14 21:51:46 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MarkForUpload: True OtherFailedConnect: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=en_US.utf-8 SHELL=/bin/bash SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/1307682 Title: samba full_audit reports wrong username when using force user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+subscriptions -- 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 1307682] [NEW] samba full_audit reports wrong username when using force user
Public bug reported: When using force user in combination with full_audit, the %U audit marco get replaced with the wrong (forced) username. This has been fixed upstream two years ago, but is not yet in precise. https://bugzilla.samba.org/show_bug.cgi?id=8882 You be great to apply this to precise as well. https://attachments.samba.org/attachment.cgi?id=7476 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: samba 2:3.6.3-2ubuntu2.10 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon Apr 14 21:51:46 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120423) MarkForUpload: True OtherFailedConnect: Yes ProcEnviron: TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 LC_MESSAGES=en_US.utf-8 SHELL=/bin/bash SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1307682 Title: samba full_audit reports wrong username when using force user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1307682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1205104] Re: 12d1:1446 Huawei E173 only detected as mass storage
I've just installed (recompiled) usb-modeswitch (2.1.0+repack0-1) and usb-modeswitch-data (20140129-1) from debian sid, removed and replugged the umts device and then suddenly the gsm devices (serial devices) turned and I could actually connect to umts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1205104 Title: 12d1:1446 Huawei E173 only detected as mass storage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1205104/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 906081] Re: Disabling 'Login without a password' does not remove user from the nopasswdlogin group
This was with a fresh saucy install (Nov 23 2013). I added a new user using gnome-control-center without setting a password. Then the admin set the password for the user, removing the automatic login toggle. Though, the user remained in the nopasswdlogin group, so it could login without any password. No indication of this was shown in gnome-control-center. By manually removing the user from that group (deluser xxx nopasswdlogin), the issue was resolved for that user. So this bug report is about not removing the user from the nopasswdlogin group. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/906081 Title: Disabling 'Login without a password' does not remove user from the nopasswdlogin group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/906081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 889942] Re: ACPI power_supply battery errors to: No such device
Still present in kernel 3.11 (saucy). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/889942 Title: ACPI power_supply battery errors to: No such device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/889942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1255592] [NEW] IPv6 Automatic, only DHCP configuration results in no default route
Public bug reported: The local network uses SLAAC configuration (with the OtherConfig-Bit in the RA set) as default configuration for devices. Some devices however should use a different IPv6 address assigned by statefull dhcp. Obviously, the ManagedConfiguration bit in the RA is not set, as this would break the SLAAC clients. When choosing Automatic, only DHCP for IPv6 configuration in the network manager (which translates into method=dhcp or NM_SETTING_IP6_CONFIG_METHOD_DHCP), the IPv6 address and the IPv6 DNS Servers are successfully assigned, but there is no ipv6 default route. This is because NM_SETTING_IP6_CONFIG_METHOD_DHCP reconfigures sysctl to drop all RAs (accept_ra=0), but DHCPv6 still has no option to set the gateway IPv6 address (neither its link-local or globally valid address). So I currently cannot have only some clients use statefull DHCPv6, which is what I want. Solution: either a) add an option to set sysctl accept_ra=1, autoconf=0 ; so the client will not use a SLAAC address but still add a default route based on RA or b) add a gateway option to DHCPv6. This bug is to change network manager so the solution a) gets implemented, as this can be implemented in NetworkManager. Solution b) would need to be implemented in isc-dhcp-client and might need an updated RFC, but would allow for different use cases (i.e. http://www.ietf.org/mail-archive/web/ipv6/current/msg08684.html). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.4 ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51 Uname: Linux 3.2.0-56-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 27 17:25:05 2013 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 141.24.40.126 dev eth0 proto static 141.24.40.64/26 dev eth0 proto kernel scope link src 141.24.40.77 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-09-19 (434 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kabelnetzwerkverbindung 1 a32a6fb7-ed99-432f-acc8-c97cc3834e76 802-3-ethernet1385569506 Mi 27 Nov 2013 17:25:06 CETyes no /org/freedesktop/NetworkManager/Settings/1 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed precise ** Description changed: The local network uses SLAAC configuration (with the OtherConfig-Bit in the RA set) as default configuration for devices. Some devices however should use a different IPv6 address assigned by statefull dhcp. Obviously, the ManagedConfiguration bit in the RA is not set, as this would break the SLAAC clients. When choosing Automatic, only DHCP for IPv6 configuration in the network manager (which translates into method=dhcp or NM_SETTING_IP6_CONFIG_METHOD_DHCP), the IPv6 address and the IPv6 DNS Servers are successfully assigned, but there is no ipv6 default route. This is because NM_SETTING_IP6_CONFIG_METHOD_DHCP reconfigures sysctl to drop all RAs (accept_ra=0), but DHCPv6 still has no option to set the gateway IPv6 address (neither its link-local or globally valid address). So I currently cannot have only some clients use statefull DHCPv6, which is what I want. Solution: either - a) set sysctl accept_ra=1, autoconf=0 ; so the client will not use a - SLAAC address but still add a default route based on RA + a) add an option to set sysctl accept_ra=1, autoconf=0 ; so the client + will not use a SLAAC address but still add a default route based on RA or b) add a gateway option to DHCPv6. This bug is to change network manager so the solution a) gets implemented, as this can be implemented in NetworkManager. Solution b) would need to be implemented in isc-dhcp-client and might need an updated RFC, but would allow for different use cases (i.e. http://www.ietf.org/mail-archive/web/ipv6/current/msg08684.html). ProblemType: Bug
[Bug 1247969] [NEW] VirtualBox kernel OOPS
Public bug reported: During Shutdown of a Ubuntu LTS guest, the following Kernel bug occurred: [38398.490888] BUG: unable to handle kernel NULL pointer dereference at 0001 [38398.490930] IP: [f97a5e7c] rtR0MemObjLinuxFreePages+0x1c/0xa0 [vboxdrv] [38398.490970] *pdpt = *pde = f000eef3f000eef3 [38398.490998] Oops: 0002 [#1] SMP [38398.491015] Modules linked in: snd_hrtimer pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) hwmon_vid k8temp snd_hda_codec_hdmi snd_hda_codec_realtek autofs4 eeepc_wmi asus_wmi sparse_keymap dm_multipath pl2303 usbserial snd_hda_intel snd_hda_codec snd_hwdep hisax snd_pcm crc_ccitt isdn hfcpci mISDN_core psmouse serio_raw snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device mac_hid snd soundcore snd_page_alloc mei(C) parport_pc eeprom ppdev i2c_nforce2 rfcomm bnep lp bluetooth parport nfsd nfs binfmt_misc lockd fscache auth_rpcgss nfs_acl sunrpc ext2 xts gf128mul dm_crypt raid10 raid456 async_raid6_recov async_pq raid6_pq async_xor async_memcpy async_tx raid0 multipath linear dm_raid45 xor dm_mirror dm_region_hash dm_log usbhid hid raid1 i915 wmi drm_kms_helper drm r8169 pata_via i2c_algo_bit video [38398.491423] [38398.491432] Pid: 5156, comm: VirtualBox Tainted: G C O 3.2.0-38-generic-pae #61-Ubuntu System manufacturer System Product Name/P8H67-M PRO [38398.491492] EIP: 0060:[f97a5e7c] EFLAGS: 00210202 CPU: 2 [38398.491522] EIP is at rtR0MemObjLinuxFreePages+0x1c/0xa0 [vboxdrv] [38398.491550] EAX: 0054 EBX: f743c410 ECX: 00400015 EDX: [38398.491578] ESI: EDI: 0018 EBP: c53fbdac ESP: c53fbda0 [38398.491605] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 [38398.491629] Process VirtualBox (pid: 5156, ti=c53fa000 task=e2de task.ti=c53fa000) [38398.491664] Stack: [38398.491673] f743c410 0018 c53fbdc0 f97a647e f743c410 0018 [38398.491715] c53fbdec f97a4ac1 e8e3ceb0 f7402380 c53fbe00 c1133707 [38398.491755] f743c410 0018 c53fbe1c f979ca5e f743c410 0001 0004 [38398.491796] Call Trace: [38398.491814] [f97a647e] rtR0MemObjNativeFree+0x14e/0x180 [vboxdrv] [38398.493566] [f97a4ac1] VBoxHost_RTR0MemObjFree+0xf1/0x2e0 [vboxdrv] [38398.495324] [c1133707] ? kfree+0xf7/0x120 [38398.497081] [f979ca5e] supdrvMemRelease+0x10e/0x150 [vboxdrv] [38398.498847] [f979cb0f] SUPR0MemFree+0x2f/0x40 [vboxdrv] [38398.500612] [f97a39b8] ? VBoxHost_RTMemFree+0x28/0x30 [vboxdrv] [38398.502372] [f97ac9c3] ? VBoxHost_RTLogSetDefaultInstanceThread+0x13/0x1d0 [vboxdrv] [38398.504134] [c116056a] ? mntput_no_expire+0x2a/0xd0 [38398.505895] [f97a297f] ? supdrvCleanupSession+0xef/0x2e0 [vboxdrv] [38398.507650] [c111af14] ? remove_vma+0x44/0x60 [38398.509405] [f97a2b8e] ? supdrvCloseSession+0x1e/0x50 [vboxdrv] [38398.511162] [f979c041] ? VBoxDrvLinuxClose+0x21/0x30 [vboxdrv] [38398.512920] [c1146518] ? __fput+0x98/0x1c0 [38398.514651] [c114665d] ? fput+0x1d/0x30 [38398.516395] [c1143414] ? filp_close+0x54/0x80 [38398.518111] [c105ca5b] ? put_files_struct.part.10+0x5b/0xa0 [38398.519838] [c105e317] ? put_files_struct+0x17/0x20 [38398.521554] [c105e3c6] ? exit_files+0x46/0x60 [38398.523257] [c105e80e] ? do_exit+0x15e/0x3c0 [38398.524949] [c12b9172] ? _copy_from_user+0x42/0x60 [38398.526627] [c105ebc8] ? do_group_exit+0x38/0xa0 [38398.528280] [c105ec48] ? sys_exit_group+0x18/0x20 [38398.529924] [c15af49f] ? sysenter_do_call+0x12/0x28 [38398.531560] [c15a007b] ? setterm_command+0xe4/0x1b5 [38398.533173] Code: eb 0d 90 90 90 90 90 90 90 90 90 90 90 90 90 55 89 e5 57 56 53 66 66 66 66 90 89 c3 8b 40 38 85 c0 74 3b 8d 74 26 00 8b 54 83 38 f0 80 62 01 fb 83 e8 01 75 f2 80 7b 34 00 8b 73 38 75 29 85 f6 [38398.536620] EIP: [f97a5e7c] rtR0MemObjLinuxFreePages+0x1c/0xa0 [vboxdrv] SS:ESP 0068:c53fbda0 [38398.538434] CR2: 0001 [38398.602669] ---[ end trace 1af8ca7fd859e6cb ]--- [38398.602672] Fixing recursive fault but reboot is needed! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: virtualbox-ose 4.1.12-dfsg-2ubuntu0.5 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic-pae 3.2.37 Uname: Linux 3.2.0-38-generic-pae i686 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Mon Nov 4 21:51:23 2013 MarkForUpload: True PackageArchitecture: all ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1247969 Title: VirtualBox kernel OOPS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1247969/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 510625] Re: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english.
hmmm. gpg does report its status and needs nicely on the status fd, and in a fixed format (NEED_PASSPHRASE...) so it looks like the gpg.py module needs to perform a bit more status_fd handling and reporting. right now it only extracts signature key ids. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/510625 Title: Bad parsing of GnuPG output, expecting english output, which doesn't work if locales different than english. To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/510625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Attachment added: screenlog.0.xz https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+attachment/3696033/+files/screenlog.0.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Attachment added: main.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+attachment/3696028/+files/main.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Attachment added: history.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+attachment/3696030/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Attachment added: lspci.txt https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+attachment/3696032/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Attachment added: apt.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+attachment/3696031/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Attachment added: apt-term.log https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+attachment/3696029/+files/apt-term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] Re: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
With my PC, this was due to /lib/ld-linux.so.2 - ld-2.15.so instead of - /lib/i386-linux-gnu/ld-linux.so.2 - /lib/i386-linux-gnu/ld-2.17.so. After fixing this, everthing worked fine. Though, /lib/ld-linux.so.2 is in libc6, so it should have been replaced during upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183682] [NEW] Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system
Public bug reported: I upgraded using console do-release-upgrade on i386 (Intel Pentium 4 HT with 64bit support) from 12.10 to 13.04. After installing a couple of packets during upgrade including libc, all subproccesses startet to segfault in libc-2.17.so , so upgrade abortet though the system was in an unusable state. Booting into initramfs gives me a console but chroot /root bash fails with a double free error and chroot ... dpkg as well as other tools still fail with libc segfault. I could not find any information about raised hardware requirements but would have expected do-release-upgrade to check for them if applicable. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: i386 raring ** Tags added: i386 raring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183682 Title: Upgrade i386 12.10 to 13.04 fails segfaulting in libc 2.17 breaking system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1183682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170463] Re: AWUS036NHR / RTL8188RU doesn't connect
still present in quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1170463 Title: AWUS036NHR / RTL8188RU doesn't connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1170463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177568] [NEW] ATI RV410 [Radeon X700 Pro (PCIE)] driver fails
Public bug reported: Hi, I upgrade this system to onerice and since then or so my radeon graphics card can only be used using the Xorg vesa driver, thus lacking bigger than 1024x768 resolution support and all the other stuff radeons driver support. The system used to work fine with precise and older ubuntu releases. The Xorg radeon driver fails with (Xorg.log) [27.806] (II) [KMS] drm report modesetting isn't supported. [27.806] (WW) Falling back to old probe method for modesetting [27.806] (EE) open /dev/dri/card0: No such file or directory [27.806] (EE) open /dev/dri/card0: No such file or directory [27.806] (WW) Falling back to old probe method for fbdev And the kernel shows in dmesg: [1.392989] [drm] radeon kernel modesetting enabled. [1.399427] radeon :01:00.0: VRAM: 128M 0xC800 - 0xCFFF (128M used) [1.399435] radeon :01:00.0: GTT: 512M 0xA800 - 0xC7FF [1.399534] radeon :01:00.0: irq 42 for MSI/MSI-X [1.399558] radeon :01:00.0: radeon: using MSI. [1.399597] [drm] radeon: irq initialized. [1.401674] [drm] radeon: 128M of VRAM memory ready [1.401678] [drm] radeon: 512M of GTT memory ready. [1.406080] [drm] radeon: 2 quad pipes, 1 z pipes initialized. [1.406197] radeon :01:00.0: WB enabled [1.406205] radeon :01:00.0: fence driver on ring 0 use gpu addr 0xa800 and cpu addr 0xffc77000 [1.521091] [drm] radeon: ring at 0xA8001000 [1.521453] radeon :01:00.0: Fatal error during modeset init [1.521465] [drm] radeon: finishing device. [1.521632] [drm] radeon: cp finalized [1.522384] radeon :01:00.0: f3678000 unpin not necessary [1.522561] [drm] radeon: ttm finalized [1.522914] radeon: probe of :01:00.0 failed with error -12 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-extra-3.5.0-28-generic 3.5.0-28.48 ProcVersionSignature: Ubuntu 3.5.0-28.48-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic i686 ApportVersion: 2.6.1-0ubuntu10 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael3352 F pulseaudio michael3400 F xfce4-volumed Date: Tue May 7 23:24:11 2013 HibernationDevice: RESUME= MachineType: MEDIONPC MS-7091 MarkForUpload: True ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-28-generic root=UUID=b08039b8-681f-4878-a516-8498f72d9e9f ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.5.0-28-generic N/A linux-backports-modules-3.5.0-28-generic N/A linux-firmware1.95.1 SourcePackage: linux UpgradeStatus: Upgraded to quantal on 2013-04-07 (30 days ago) dmi.bios.date: 04/01/2005 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: MS-7091 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd04/01/2005:svnMEDIONPC:pnMS-7091:pvr:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7091:rvr:cvn:ct3:cvr: dmi.product.name: MS-7091 dmi.sys.vendor: MEDIONPC ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug i386 quantal ** Attachment added: Xorg.0.log https://bugs.launchpad.net/bugs/1177568/+attachment/3669193/+files/Xorg.0.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177568 Title: ATI RV410 [Radeon X700 Pro (PCIE)] driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177568] Re: ATI RV410 [Radeon X700 Pro (PCIE)] driver fails
The kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.9-raring/ fixes the problem for me. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177568 Title: ATI RV410 [Radeon X700 Pro (PCIE)] driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1177568] Re: ATI RV410 [Radeon X700 Pro (PCIE)] driver fails
dmesg on kernel 3.9.0-030900-generic [1.961649] [drm] radeon kernel modesetting enabled. [1.967058] radeon :01:00.0: VRAM: 128M 0xC800 - 0xCFFF (128M used) [1.967077] radeon :01:00.0: GTT: 512M 0xA800 - 0xC7FF [1.967243] radeon :01:00.0: irq 42 for MSI/MSI-X [1.967288] radeon :01:00.0: radeon: using MSI. [1.967356] [drm] radeon: irq initialized. [1.984446] [drm] radeon: 128M of VRAM memory ready [1.984451] [drm] radeon: 512M of GTT memory ready. [1.988845] [drm] radeon: 2 quad pipes, 1 z pipes initialized. [1.988904] radeon :01:00.0: WB enabled [1.988914] radeon :01:00.0: fence driver on ring 0 use gpu addr 0xa800 and cpu addr 0xffc95000 [1.989447] [drm] radeon: ring at 0xA8001000 [2.040108] fbcon: radeondrmfb (fb0) is primary device [2.111464] radeon :01:00.0: fb0: radeondrmfb frame buffer device [2.111470] radeon :01:00.0: registered panic notifier [2.111484] [drm] Initialized radeon 2.30.0 20080528 for :01:00.0 on minor 0 ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1177568 Title: ATI RV410 [Radeon X700 Pro (PCIE)] driver fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 989496] Re: UnicodeDecodeError during backup due to non-utf8 translation
i've dug into this a bit more deeply and found an explanation for the
logging gotchas under certain locales:
as per the python wiki
(http://web.archive.org/web/20120425192131/http://wiki.python.org/moin/UnicodeEncodeError)
when you run somestring.decode(whicheverencoding) python2 does weird
encode-and-then-decode things if your somestring is already unicode.
log.py uses s.decode('utf8',ignore) - which fails to ignore errors on
some locales (apparently in the down-EN-coding step before the
decode...).
check out the attached test script, which contains an iso8859 string to
log. if you run it (at least under python 2.6) with LC_CTYPE=anything
utf8 or plain C/POSIX then it works fine. if your CTYPE is iso88591,
then the first decode of x works but the second decode fails, and we get
the ascii can't encode complaint.
i've just changed the debian version (0.6.20-2) to do the decode in
log.py conditionally:
_logger.log(DupToLoggerLevel(verb_level), s if (isinstance(s,unicode))
else s.decode(utf8, ignore))
regards,
az
** Attachment added: test script for the decode-ascii-issue
https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/989496/+attachment/3483743/+files/dreck.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989496
Title:
UnicodeDecodeError during backup due to non-utf8 translation
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/989496/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 786524] Re: banshee does not display CD TEXT
still present in quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/786524 Title: banshee does not display CD TEXT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/786524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
