[Bug 2068030] Re: No drivers detected for TU104GL [T4G] card
sos report of the jammy host ** Attachment added: "sosreport-ip-172-31-19-168-2024-06-04-gtcbeon.tar.xz" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+attachment/5785859/+files/sosreport-ip-172-31-19-168-2024-06-04-gtcbeon.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068030 Title: No drivers detected for TU104GL [T4G] card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068030] [NEW] No drivers detected for TU104GL [T4G] card
Public bug reported: ubuntu-drivers is not returning any driver for g5g instances in AWS, which use Tesla T4G cards: # lspci -tv -[:00]-+-00.0 Amazon.com, Inc. Device 0200 +-01.0 Amazon.com, Inc. Device 8250 +-04.0 Amazon.com, Inc. NVMe EBS Controller +-05.0 Amazon.com, Inc. Elastic Network Adapter (ENA) \-1f.0 NVIDIA Corporation TU104GL [T4G] # ubuntu-drivers --gpgpu list This is gpgpu mode # uname -a Linux ip-172-31-16-212 6.8.0-1008-aws #8-Ubuntu SMP Sat Apr 20 02:43:14 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 24.04 LTS Release:24.04 Codename: noble Processor: Handle 0x0004, DMI type 4, 42 bytes Processor Information Socket Designation: CPU00 Type: Central Processor Family: ARMv8 Manufacturer: AWS ID: C1 D0 3F 41 00 00 00 00 Signature: Implementor 0x41, Variant 0x3, Architecture 15, Part 0xd0c, Revision 1 Version: AWS Graviton2 I tried Noble and Jammy and both have the same behavior. Manually installing the drivers works as expected (below is the output in Jammy, as Noble is hitting https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-550-server/+bug/2062380 and freezes on module loading) $ sudo nvidia-smi Tue Jun 4 14:18:15 2024 +---+ | NVIDIA-SMI 535.161.08 Driver Version: 535.161.08 CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA T4G Off | :00:1F.0 Off | 0 | | N/A 36CP0 27W / 70W | 2MiB / 15360MiB | 4% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| | No running processes found | +---+ ** Affects: ubuntu-drivers-common (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/2068030 Title: No drivers detected for TU104GL [T4G] card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2068030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061068] Re: debsums check failed
Weichen, this was a bug on the snapd package until version 2.61.2: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2057491 snapd is now updated to 2.61.3 and the issue is fixed. It's unrelated to the changes you made. I also tried to reproduce it in my environment with a fresh installation and the issue didn't manifest, so I can confirm it's fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061068 Title: debsums check failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060239] [NEW] instalation failed
Public bug reported: A fatal error was reported during installation. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity 22.04.20 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.470.2 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 4 18:21:54 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) ProcEnviron: LANGUAGE=pt_BR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubiquity-22.04.20 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060239 Title: instalation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/2060239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973619] Re: Sane net autodiscovery not working in 22.04
For evidence purposes, I'm attaching the output of 'iptables-save' in my Ubuntu 22.04 machine. ** Attachment added: "iptables-save.txt" https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+attachment/5590257/+files/iptables-save.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973619 Title: Sane net autodiscovery not working in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973619] Re: Sane net autodiscovery not working in 22.04
Once I turn the firewall off, the autodiscovery starts working (without any changes to /etc/sane.d/epson2.conf): # service ufw stop # scanimage -L device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner If I reload the firewall rules, the autodiscovery stops working again. This is probably the only relevant difference between my Ubuntu 21.10 and my Ubuntu 22.04 installations. Perhaps the stock firewall rules should be amended to make them autodiscovery-friendly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973619 Title: Sane net autodiscovery not working in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973619] Re: Sane net autodiscovery not working in 22.04
Yes, it is: $ dpkg --get-selections *sane* libsane-common install libsane-hpaio:amd64 install libsane1:amd64 install sane-airscaninstall sane-utils install The exact same set of packages installed in my Ubuntu 21.10. The only difference are the versions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973619 Title: Sane net autodiscovery not working in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973619] [NEW] Sane net autodiscovery not working in 22.04
Public bug reported: I have used every Ubuntu version since 16.10 and on all of them my network scanner EPSON SX525WD could be discovered out of the box. On 22.04 the output of 'scanimage -L' is: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). To double-check if something hadn't changed in my network, I opened a laptop which still has Ubuntu 21.10 installed. I ran 'scanimage -L' and it shows: device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner device `airscan:w0:EPSON Epson Stylus SX525WD' is a WSD EPSON Epson Stylus SX525WD ip=192.168.8.8 My current workaround for 22.04 is to append the line: net 192.168.8.8 to /etc/sane.d/epson2.conf. The command 'scanimage -L' detects the scanner (albeit no 'airscan' result shows up): device `epson2:net:192.168.8.8' is a Epson PID 085E flatbed scanner NOTE: I filled this bug under the 'sane-backends' package because this form gave this error: "sane-utils" does not exist in Ubuntu ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sane-utils 1.1.1-5 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 16 15:53:46 2022 InstallationDate: Installed on 2020-02-02 (833 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: sane-backends UpgradeStatus: Upgraded to jammy on 2022-05-06 (9 days ago) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973619 Title: Sane net autodiscovery not working in 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1973619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970984] Re: Can't save files in a Folder in a Folder 22.04
Checking https://askubuntu.com/questions/1405901/ubuntu-22-04-ui-issues- in-app-file-selector-save-prompt-saving-files-and-new-w I can confirm that it's possible to work around this bug if edit the name of the file to be saved, just adding any character to the filename and it will be saved in any folder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970984 Title: Can't save files in a Folder in a Folder 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970984] Re: Can't save files in a Folder in a Folder 22.04
I tried downloading files using google chrome and firefox and the behavior is the same. If I try to save the file to my homedir the file is downloaded, if I try to save to /tmp it also works, but if I try to save to any other folder it doesn't work, the download doesn't start. I downloaded firefox in version 91.0.0-esr https://ftp.mozilla.org/pub/firefox/releases/91.8.0esr/linux-x86_64/en-US/firefox-91.8.0esr.tar.bz2 And I was able to save files in any folder. I also noticed that when opening the download window I get the following log using sudo journalctl -f Apr 30 13:27:14 vortex gnome-shell[135810]: Can't update stage views actor [:0x559239a7c370] is on because it needs an all occasion. Apr 30 13:27:14 vortex gnome-shell[135810]: Can't update stage views actor [:0x559239f75af0] is on because it needs an allocation. Apr 30 13:27:14 vortex gnome-shell[135810]: Can't update stage views actor [:0x55923b951830] is on because it needs an allocation. Ubuntu 22.04 on X11, fully updated 30/04/2022 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970984 Title: Can't save files in a Folder in a Folder 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970282] Re: Flatpak apps are not properly themed if a accent color other than the default is choosed
For a Flatpak application to follow the system theme in use, the corresponding Flatpak theme needs to be installed. For example, if I use the "Yaru" theme in "Dark mode" with the "Prussian Green" accent color, the "org.gtk.Gtk3theme.Yaru-prussiangreen-dark" needs to be installed. If it is, both system applications and Flatpak applications look consistent. However, only a few themes are available in the Flathub repos. If you search for Yaru themes on Flathub (flatpak search Yaru), you will notice there are alot of variations, but only the packages not presenting a "Version" number correspond to the new 22.04 Yaru theme. As such, only the following Yaru (22.04) themes have a correspondent Flatpak theme: Yaru Yaru-dark Yaru-sage Yaru-bark Yaru-bark-dark Yaru-prussiangreen Yaru-prussiangreen-dark Yaru-olive Yaru-olive-dark Yaru-magenta Yaru-magenta-dark For a consistent look between Flatpak and non-Flatpak applications in Ubuntu 22.04, the missing accent color themes need to be available in Flathub. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970282 Title: Flatpak apps are not properly themed if a accent color other than the default is choosed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1970282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947000] [NEW] package mysql-server-8.0 8.0.26 failed to install
Public bug reported: package mysql-server-8.0 8.0.26 failed to install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Oct 13 12:10:42 2021 ErrorMessage: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-02-07 (614 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Muitos níveis de links simbólicos: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['ca.pem', 'corona01', 'server-key.pem', 'undo_001', 'undo_002', 'mysql', 'ib_logfile0', 'corona', 'sys', 'mysql.ibd', '#innodb_temp', 'ib_buffer_pool', 'binlog.index', 'private_key.pem', 'ca-key.pem', 'client-key.pem', 'client-cert.pem', '#ib_16384_0.dblwr', 'public_key.pem', 'ibdata1', 'performance_schema', 'binlog.000582', 'binlog.000581', '#ib_16384_1.dblwr', 'binlog.000580', 'auto.cnf', 'ib_logfile1', 'server-cert.pem', 'mysql_upgrade_info', 'debian-5.7.flag'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.26-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-05-08 (523 days ago) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947000 Title: package mysql-server-8.0 8.0.26 failed to install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1947000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939243] [NEW] i don´t know
Public bug reported: i don´t know ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompositorRunning: None Date: Sun Aug 8 13:11:24 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS Rev. 2] [1462:1162] InstallationDate: Installed on 2016-12-02 (1710 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Itautec S.A. Infoway ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=357307e7-3637-4156-9d71-68dd5895191e ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: Itautec ST 1350 BIOS 0203-SL2, 06/27/2007 dmi.board.name: ST 1350 dmi.board.vendor: Itautec S.A. dmi.board.version: ST-1350 Padrao 02(Itautec_M) dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrItautecST1350BIOS0203-SL2,06/27/2007:bd06/27/2007:svnItautecS.A.:pnInfoway:pvrCorp:rvnItautecS.A.:rnST1350:rvrST-1350Padrao02(Itautec_M):cvnChassisManufacture:ct3:cvr: dmi.product.name: Infoway dmi.product.version: Corp dmi.sys.vendor: Itautec S.A. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Sun Aug 8 13:01:17 2021 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputSIGMACHIP Usb Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.11-1ubuntu1.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939243 Title: i don´t know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1939243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777708] Re: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg)
I'm here to say that I'm having the same issue. Until this evening, I was using Debian 10 with KDE, but I installed Ubuntu 20.04 a few hours ago. I use a laptop with a external keyboard connected on it and my laptop have a numeric keyboard and my external keyboard don't, so I always use the laptop keyboard to insert numbers. However, each time I swap the keyboard, my computer frozen. Also, I have a mouse with several buttons and two of them are configured as "PgUp" and "PgDn" because I find it more practical over there. However, unfortunately, I can't use it properly because the computer crashes every time I press a button. However, I think it's worth mentioning that mouse buttons that belong to the mouse (like click and scroll) don't have this problem. In short, if I switch keyboards, whether it's laptop, external or mouse buttons, my computer freezes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/108 Title: Desktop briefly becomes unresponsive when receiving a keypress from a different device/mapping than the last keypress (in Xorg) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/108/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936750] [NEW] package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-xdg 0.25-4ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Sun Jul 18 14:24:21 2021 Dependencies: ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 139 InstallationDate: Installed on 2016-12-02 (1689 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: pyxdg Title: package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pyxdg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936750 Title: package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyxdg/+bug/1936750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928479] [NEW] package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade:
Public bug reported: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 AptOrdering: mysql-server-8.0:amd64: Install mysql-server-core-8.0:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 14 12:02:35 2021 ErrorMessage: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-02-07 (462 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLVarLibDirListing: ['ca.pem', 'binlog.000477', 'corona01', 'binlog.000495', 'binlog.000478', 'binlog.000475', 'server-key.pem', 'undo_001', 'undo_002', 'mysql', 'ib_logfile0', 'binlog.000483', 'corona', 'binlog.000489', 'binlog.000493', 'sys', 'binlog.000488', 'binlog.000492', 'binlog.000484', 'binlog.000487', 'mysql.ibd', '#innodb_temp', 'ib_buffer_pool', 'binlog.index', 'binlog.000480', 'private_key.pem', 'ca-key.pem', 'binlog.000486', 'client-key.pem', 'client-cert.pem', 'binlog.000479', '#ib_16384_0.dblwr', 'public_key.pem', 'binlog.000496', 'binlog.000494', 'ibdata1', 'performance_schema', 'binlog.000485', '#ib_16384_1.dblwr', 'binlog.000481', 'binlog.000476', 'auto.cnf', 'ib_logfile1', 'server-cert.pem', 'binlog.000491', 'mysql_upgrade_info', 'debian-5.7.flag', 'binlog.000482', 'binlog.000490'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 UpgradeStatus: Upgraded to focal on 2020-05-08 (371 days ago) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928479 Title: package mysql-server-8.0 8.0.25-0ubuntu0.20.04.1 failed to install/upgrade: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1928479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921187] Re: Illegal instruction at start − sse3 required on i386
This situation also affects me. When I updated the chromium-browser, it stopped to function. I tried to install an older version (65.0.3325.181-0ubuntu1), but there are conflicts with needed packages (chromium-codecs-ffmpeg-extra chromium-codecs-ffmpeg) once it doesn't try to install the older version of them but the most recent version. Any help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921187 Title: Illegal instruction at start − sse3 required on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1921187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883753] Re: The 64-bit and 32-bit packages conflict
This issue also affects arm64 and armhf architetures, making it currently impossible for me to complete installation of my crossbuild environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883753 Title: The 64-bit and 32-bit packages conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opusfile/+bug/1883753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895064] [NEW] table to upgrade error
Public bug reported: stopped the upgrade because the tables to apt is incorrect... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.30 ProcVersionSignature: Ubuntu 4.4.0-189.219-powerpc-smp 4.4.232 Uname: Linux 4.4.0-189-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2.24 Architecture: powerpc CrashDB: ubuntu Date: Wed Sep 9 19:41:01 2020 InstallationDate: Installed on 2018-05-27 (836 days ago) InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release powerpc (20140416.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2020-09-09 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-09-09 19:37:57.720191 Log time: 2020-09-09 19:38:05.559431 Log time: 2020-09-09 19:39:56.443980 Log time: 2020-09-09 19:41:14.122989 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dist-upgrade powerpc xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895064 Title: table to upgrade error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1895064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
this affects me for some years now, bosses now complain for me to move to windows as now we are all remote with tons of meetings and this is a big impact on how they see all this linux desktop adoption. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867424] Re: motd-news transmitting private hardware data without consent or knowledge in background
Well, it is disappointing that you choose to close this as “won’t fix”. As pointed out in the initial bug report, this “feature” is implemented without notice or consent. In other words, and to rephrase, this was done transparently in an hidden way. Which is, to say the least, not corresponding to standard usage and best practices, let alone the security aspect by running it as root. This is definitely not very reassuring for users who are left with the suspicion, confirmed by the manager of the Ubuntu Server team, that Ubuntu is comfortable implementing (and might implement in the future) this kind of “features” and data collection without further notice or consent from the users. As professional users we have already our share of burden to protect our assets from all kinds of threats, being obliged to add to that list the base OS leaves us with no other choice but to reconsider Ubuntu as a (un)trusted provider. Sad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867424 Title: motd-news transmitting private hardware data without consent or knowledge in background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1867424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838129] Re: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap
@sergiusens Fantastic findings! Thanks a lot for looking into this. This is also the underlying issue behind another issue I face when selfhosting VS Code: it simply crashes when opening a native Open dialog. Unsetting those env vars also fixes that issue! We got that bootstrapping code from Martin (@flexiondotorg): https://github.com/snapcrafters/vscode/commit/1477ff8a6b80d3e337ffabf75c2c9e3482b8ab74 Including a tiny review from you: https://github.com/snapcrafters/vscode/commit/1477ff8a6b80d3e337ffabf75c2c9e3482b8ab74#r32657237 I didn't really understand the original motive behind the `Gdk-pixbuf loaders` section. What do you think we can do here? What's the right way to move forward? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838129 Title: Firefox crashreporter crashed with SIGSEGV in memcpy() when opening links from Visual Studio Code snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1838129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843036] Re: [regression] SNMP missing disks in hrStorageTable
We have a similar problem with the Nagios: (...) OID : 1.3.6.1.2.1.25.2.3.1.2.1, Storagetype: Ram ?= FixedDisk OID : 1.3.6.1.2.1.25.2.3.1.3.7, Desc : Cached memory OID : 1.3.6.1.2.1.25.2.3.1.2.7, Storagetype: Other ?= FixedDisk storages selected : 0 Unknown storage : /home$ : ERROR After downgrade: (..) OID : 1.3.6.1.2.1.25.2.3.1.3.40, Desc : /run/lock OID : 1.3.6.1.2.1.25.2.3.1.2.40, Storagetype: FixedDisk ?= FixedDisk Name : /run/lock, Index : 40 OID : 1.3.6.1.2.1.25.2.3.1.3.73, Desc : /home/ (...) All selected storages (<90%) : OK -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843036 Title: [regression] SNMP missing disks in hrStorageTable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1843036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789214] Re: Clevo N850EL crashes / freezes under Ubuntu 18.04.1
Just for information, that trying out Ubuntu 18.10 kernel 4.18.0-10-generic booting from USB pen, the problem remains (and the intel_idle.max_cstate=1 workaround still works). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799577] [NEW] package grub-pc 2.02-2ubuntu8.6 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1
Public bug reported: I have a Lubuntu installation, in which I cannot upgrade because grub2-pc refuses to install. After a while I found that linux- image-4.15.0.38-generic also not installs, but grub2 in the main one, because every apt installation is extremely long, since it tries to install grub2, but it cannot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-pc 2.02-2ubuntu8.6 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 23 17:46:39 2018 ErrorMessage: installed grub-pc package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-09-20 (33 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3a1dadee-21a1-41ca-a739-bc432c4a9312 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: grub2 Title: package grub-pc 2.02-2ubuntu8.6 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799577 Title: package grub-pc 2.02-2ubuntu8.6 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1799577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.
** Also affects: apport Importance: Undecided Status: New ** No longer affects: apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787729 Title: [FAILED] Failed to start Process error reports when automatic reporting is enabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789214] Re: Clevo N850EL crashes / freezes under Ubuntu 18.04.1
** 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/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789214] Re: Clevo N850EL crashes / freezes under Ubuntu 18.04.1
Good evening! I can give feedback right away from the last 2 notes. The other workaround proposed (in askubuntu.com) of adding a kernel parameter intel_idle.max_cstate=1 seems to work well (max uptime tested is 6h 45min so far). Regarding the indication to use 4.18.3-041803-generic, I downloaded and installed the packages (for my own record): linux-headers-4.18.3-041803_4.18.3-041803.201808180530_all.deb linux-headers-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb linux-image-unsigned-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb linux-modules-4.18.3-041803-generic_4.18.3-041803.201808180530_amd64.deb The boot cmdline was: root@jpsl-N8xxEL:~# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.18.3-041803-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text ( ( Note that, it is without intel_idle.max_cstate=1 ) the kernel 4.18.3-041803-generic crashes / freezes frequently also. Already tested 3 times, so I added the tag kernel-bug-exists-upstream (I should also mention that if I give the command "reboot" or "poweroff" using this kernel, it always freezes - but I don't know if this is related or not). ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789214] Re: Clevo N850EL crashes / freezes under Ubuntu 18.04.1
> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? No upgrade. This is a fresh install, on a brand new laptop computer. > Please test the latest v4.18 kernel[0]. I've tested the mainline kernel build v4.18.5, 2 days ago, which showed the same problem. Tomorrow, I will test another proposed work-around of adding kernel parameter intel_idle.max_cstate=1 for about 8 hours. (It is looking good today, but only 1 hour of uptime so far...) Then I will test the v4.18.3 kernel (if ok, the test will take at least 8 hours - 1 full day of work), and I will give feedback here. Thank you for feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789214] [NEW] Clevo N850EL crashes / freezes under Ubuntu 18.04.1
Public bug reported: The details of what I've attempted so far are in https://askubuntu.com/questions/1068161/clevo-n850el-crashes-freezes- ubuntu-18-04-1-frequently Any workaround help greatly appreciated. (I do not need NVIDIA graphics, but I do need VirtualBox). Regards, ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jpsl 1955 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Aug 27 14:56:57 2018 InstallationDate: Installed on 2018-08-22 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:2110 Acer, Inc Bus 001 Device 004: ID 0461:4de3 Primax Electronics, Ltd Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N8xxEL ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=60daf8a6-ead0-4dc1-9b51-e7fa0fd7304c ro text crashkernel=384M-:4096M RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.004 dmi.board.asset.tag: Tag 12345 dmi.board.name: N8xxEL dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.004:bd04/27/2018:svnNotebook:pnN8xxEL:pvrNotApplicable:rvnNotebook:rnN8xxEL:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N8xxEL dmi.product.version: Not Applicable dmi.sys.vendor: Notebook ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** 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/1789214 Title: Clevo N850EL crashes / freezes under Ubuntu 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782395] [NEW] package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 "apareceu do nada"
*** This bug is a duplicate of bug 1781849 *** https://bugs.launchpad.net/bugs/1781849 Public bug reported: apareceu isso do nada ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Jul 15 21:42:36 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python3-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782395 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 "apareceu do nada" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1782395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782145] [NEW] package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 10
Public bug reported: how to fix? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.2-0ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 17 09:30:49 2018 ErrorMessage: installed gdm3 package pre-removal script subprocess returned error exit status 10 InstallationDate: Installed on 2018-06-02 (44 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.2 SourcePackage: gdm3 Title: package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.Init.Default: 2018-07-04T05:31:34.285178 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782145 Title: package gdm3 3.28.2-0ubuntu1.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782145/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677370] Re: very slow file copying in Ubuntu 16.04 to and from external hard drive
Same here. Ubuntu 16.04 64 Bits @ Dell Inspiron 7560 (i7 16 GB RAM) 1 SSD + 1 HDD Even copying via CLI. Same USB Stick, same computer but with windows 10 = very fast. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677370 Title: very slow file copying in Ubuntu 16.04 to and from external hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1677370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757405] [NEW] Upgrade from 16.04 to 17.10 failed
Public bug reported: No further information ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.24 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CrashDB: ubuntu Date: Wed Mar 21 11:14:18 2018 InstallationDate: Installed on 2017-06-21 (272 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2018-03-21 (0 days ago) VarLogDistupgradeAptlog: Log time: 2018-03-21 11:14:00.383965 Log time: 2018-03-21 11:14:02.492261 Log time: 2018-03-21 11:14:15.61 Log time: 2018-03-21 11:14:20.688855 VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2018-03-12T15:11:15.316597 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757405 Title: Upgrade from 16.04 to 17.10 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1757405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1543192] Re: Xorg crashed with SIGABRT in OsAbort() ["no screens found"]
It happens to me to. Usually, when I click (with mouse) at some panel element (calendar, configuration icon etc.). I've a Dell Notebook with NVidia on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543192 Title: Xorg crashed with SIGABRT in OsAbort() ["no screens found"] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740033] Re: [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only
** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740033 Title: [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1740033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740033] [NEW] [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only
Public bug reported: I've upgraded my computer to a new one with a Realtek ALC1220 from an ASUS crosshair VI hero and on my ubuntu 17.10 my 5.1 surround left audio is busted, I've configured the system audio to 5.1 and tested all speakers one by one and the only one that isn't working correctly is the left speaker, it emits the testing sound but is disturbed and very low, I've checked alsaconf and everything is alright there. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13 Uname: Linux 4.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: biohazard 1481 F pulseaudio /dev/snd/controlC1: biohazard 1481 F pulseaudio CurrentDesktop: GNOME Date: Mon Dec 25 15:39:30 2017 InstallationDate: Installed on 2017-12-25 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: HD-Audio Generic - HD-Audio Generic Symptom_Jack: Green Line Out, Rear Symptom_Type: High background noise, or volume is too low Title: [System Product Name, Realtek ALC1220, Green Line Out, Rear] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3008 dmi.board.asset.tag: Default string dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3008:bd11/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740033 Title: [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1740033/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1738379] Re: Install and configure for Ubuntu in horizon
glad I could help! regards, Joao On 12/19/2017 06:00 PM, Corey Bryant wrote: > Hi All, thanks for reporting this. I've pushed a fix the Queens package > that will be included in the next Queens upload of horizon. > > ** Changed in: horizon (Ubuntu) > Status: Triaged => Fix Committed > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1738379 Title: Install and configure for Ubuntu in horizon To manage notifications about this bug go to: https://bugs.launchpad.net/horizon/+bug/1738379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1723451] Re: package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
root@jonas-X541UV:/home/jonas# strace plymouth --ping execve("/bin/plymouth", ["plymouth", "--ping"], [/* 84 vars */]) = 0 brk(NULL) = 0x55c8840d8000 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) mmap(NULL, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f321b623000 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3 fstat(3, {st_mode=S_IFREG|0644, st_size=246346, ...}) = 0 mmap(NULL, 246346, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f321b5e6000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libply.so.4", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\E\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0644, st_size=88632, ...}) = 0 mmap(NULL, 2185728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f321b1e9000 mprotect(0x7f321b1fe000, 2093056, PROT_NONE) = 0 mmap(0x7f321b3fd000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x14000) = 0x7f321b3fd000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\22\2\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=1960656, ...}) = 0 mmap(NULL, 4061792, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f321ae09000 mprotect(0x7f321afdf000, 2097152, PROT_NONE) = 0 mmap(0x7f321b1df000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1d6000) = 0x7f321b1df000 mmap(0x7f321b1e5000, 14944, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f321b1e5000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/lib/x86_64-linux-gnu/librt.so.1", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\0\"\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0644, st_size=31744, ...}) = 0 mmap(NULL, 2128864, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f321ac01000 mprotect(0x7f321ac08000, 2093056, PROT_NONE) = 0 mmap(0x7f321ae07000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7f321ae07000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libdl.so.2", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\220\16\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0644, st_size=14632, ...}) = 0 mmap(NULL, 2109712, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f321a9fd000 mprotect(0x7f321aa0, 2093056, PROT_NONE) = 0 mmap(0x7f321abff000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x2000) = 0x7f321abff000 close(3) = 0 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory) openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpthread.so.0", O_RDONLY|O_CLOEXEC) = 3 read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\360a\0\0\0\0\0\0"..., 832) = 832 fstat(3, {st_mode=S_IFREG|0755, st_size=144776, ...}) = 0 mmap(NULL, 2221160, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7f321a7de000 mprotect(0x7f321a7f8000, 2093056, PROT_NONE) = 0 mmap(0x7f321a9f7000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x19000) = 0x7f321a9f7000 mmap(0x7f321a9f9000, 13416, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f321a9f9000 close(3) = 0 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7f321b5e4000 arch_prctl(ARCH_SET_FS, 0x7f321b5e5480) = 0 mprotect(0x7f321b1df000, 16384, PROT_READ) = 0 mprotect(0x7f321a9f7000, 4096, PROT_READ) = 0 mprotect(0x7f321abff000, 4096, PROT_READ) = 0 mprotect(0x7f321ae07000, 4096, PROT_READ) = 0 mprotect(0x7f321b3fd000, 4096, PROT_READ) = 0 mprotect(0x55c882edf000, 4096, PROT_READ) = 0 mprotect(0x7f321b626000, 4096, PROT_READ) = 0 munmap(0x7f321b5e6000, 246346) = 0 set_tid_address(0x7f321b5e5750) = 7346 set_robust_list(0x7f321b5e5760, 24) = 0 rt_sigaction(SIGRTMIN, {sa_handler=0x7f321a7e3c70, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x7f321a7f1150}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {sa_handler=0x7f321a7e3d00, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x7f321a7f1150}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 prlimit64(0, RLIMIT_STACK, NULL, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 rt_sigaction(SIGPIPE, {sa_handler=SIG_IGN, sa_mask=[PIPE],
Re: [Bug 1723451] Re: package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hello, Yes, 'plymouth --ping' runs forever with my user and with sudo. jonas@jonas-X541UV:~$ plymouth --ping I've solved this issue using 'killall plymouth' in another term. Thanks in advance On 18-10-2017 20:51, Brian Murray wrote: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please check to see if the command 'plymouth --ping' > continues to hang in a terminal. In the event that it does it would > help us out if you could run it under strace e.g. 'strace plymouth > --ping' so that we can determine why the process is hanging. Thanks for > your assistance! > > ** Changed in: grub2 (Ubuntu) >Status: Confirmed => Incomplete > > ** Changed in: plymouth (Ubuntu) >Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723451 Title: package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1723451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1638420] Re: LVM install with Lubuntu fails due to missing lvm2 package
I can try this weekend with 17.10, I never could install 17.10 via ISO because my usb wifi stopped working there right at the installation also. I spent several hours trying to understand the problem, but i couldn't. This is the card: https://www.newegg.com/Product/Product.aspx?Item=N82E16833320089 Do you want me to test the ISO install of 17.10 this weekend and reply back in this e-mail? Cheers On Wed, Oct 18, 2017 at 4:37 AM, Simon Quigleywrote: > Is this still an issue with the 17.10 ISO? > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1699671). > https://bugs.launchpad.net/bugs/1638420 > > Title: > LVM install with Lubuntu fails due to missing lvm2 package > > Status in Lubuntu Next: > New > Status in lubuntu-meta package in Ubuntu: > Triaged > > Bug description: > Attempting to install Lubuntu using LVM crashes because the lvm2 > package is missing from the image. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/lubuntu-next/+bug/1638420/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638420 Title: LVM install with Lubuntu fails due to missing lvm2 package To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-next/+bug/1638420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1723451] [NEW] package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Setting up grub-common (2.02~beta3-4ubuntu7) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Job for grub-common.service failed because a timeout was exceeded. See "systemctl status grub-common.service" and "journalctl -xe" for details. invoke-rc.d: initscript grub-common, action "start" failed. ● grub-common.service - LSB: Record successful boot for GRUB Loaded: loaded (/etc/init.d/grub-common; generated; vendor preset: enabled) Active: failed (Result: timeout) since Fri 2017-10-13 15:49:09 WEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 13224 ExecStart=/etc/init.d/grub-common start (code=killed, signal=TERM) Tasks: 2 (limit: 4915) CGroup: /system.slice/grub-common.service └─13228 plymouth --ping out 13 15:44:09 jonas-X541UV systemd[1]: Starting LSB: Record successful boot for GRUB... out 13 15:49:09 jonas-X541UV systemd[1]: grub-common.service: Start operation timed out. Terminating. out 13 15:49:09 jonas-X541UV systemd[1]: Failed to start LSB: Record successful boot for GRUB. out 13 15:49:09 jonas-X541UV systemd[1]: grub-common.service: Unit entered failed state. out 13 15:49:09 jonas-X541UV systemd[1]: grub-common.service: Failed with result 'timeout'. dpkg: error processing package grub-common (--configure): subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 17.10 Package: grub-common 2.02~beta3-4ubuntu7 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Fri Oct 13 15:49:09 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-07-28 (76 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash pci=nomsi vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: grub2 Title: package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1723451 Title: package grub-common 2.02~beta3-4ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1723451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711099] [NEW] grub was unable to install itself on a Dell Inspiron notebook previously windows
Public bug reported: The installation cancels at 80% ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.4 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: Wed Aug 16 07:06:10 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=pt_BR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.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/1711099 Title: grub was unable to install itself on a Dell Inspiron notebook previously windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1711099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703091] Re: Kernel panic - not syncing: Fatal exception in interrupt
Replying to note 12, (I'm the guy with the Clevo P150SM) Kernel 4.4.0-83.106 crashed on boot (with the same error) 4 out of 5 times. Kernel 4.4.0-87.110 crashed 0 (zero) out of 5 times. I am keeping 4.4.0-87 for now (and removed 4.4.0-87). PS: Something weird happening while installing 4.4.0-87.110 using the normal graphical About this computer, Check of updates. The linux- headers were not installed (and virtualbox became broken). I manually installed the headers with # apt install linux-headers-`uname -r` rebooted, and everything was fine afterwards. PS2: kernel 4.4.76-040476 worked fine all this time (running virtualbox everyday) since note 11 on 2017-07-11:. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703091 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703723] [NEW] package dolibarr (not installed) failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1
Public bug reported: I try to install Dolibarr in my pc. But after a lot of problems with the LAMP, I gave up. And now there is a message that is displayed to me every time I access my pc. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: dolibarr (not installed) ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun Jul 9 18:38:34 2017 ErrorMessage: subprocesso script post-installation instalado retornou erro do status de saída 1 InstallationDate: Installed on 2017-04-26 (76 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: dolibarr Title: package dolibarr (not installed) failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apache2.conf-available.dolibarr.conf: [deleted] modified.conffile..etc.dolibarr.default-paths.php: [deleted] modified.conffile..etc.dolibarr.install.forced.php: [deleted] ** Affects: dolibarr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703723 Title: package dolibarr (not installed) failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolibarr/+bug/1703723/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703091] Re: Kernel panic - not syncing: Fatal exception in interrupt
Answering to note 7, >From 12 boot sequences (there was 2 seconds waiting in power-off mode before starting the next boot), the results where: Kernel 4.4.0-83.106 crashed on boot (with the same error) 5 out of 6 times. Kernel 4.4.76-040476 crashed 0 (zero) out of 6 times. Looking good for 4.4.76-040476! PS: No errors while installing kernel 4.4.76-040476, and virtualbox seems fine running too, although not relevant for now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703091 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703091] Re: Kernel panic - not syncing: Fatal exception in interrupt
Answering first to note 5, yes. All the times that kernel 4.4.0-83 crashed, the problem goes away if I boot my previous kernel 4.4.0-81. kernel 4.4.0-83.106 does not crash during all the boots. Only some times. I could not figure out if they are related to cold/hot boots (in the morning always suceeds, thank goodness), CPU temperature, or any other factor. Answering to note 4, regarding the 4.12.0-041200.201707022031 kernel it appears to solve the problem, but I can't be 100% sure. Using the grub Advanced Ubuntu options, I performed 12 reboots, 6 reboots of each kernel 4.4.0-83.106 and 4.12.0-041200.201707022031 interleaved (boot 4.4.0-83.106, then reboot 4.12.0-041200, then reboot 4.4.0-83.106, etc...) Kernel 4.4.0-83.106 crashed on boot (with the same error) 3 out of 6 times. Kernel 4.12.0-041200 crashed 0 (zero) out of 6 times. Not all reboots took a 5 second power-off interval. (The ones that kernel 4.4.0-83 crashed, did wait a few seconds before booting again). So, the fix looks promising. Meanwhile, I go back to kernel 4.4.0-83 or 4.4.0-81 because I need virtualbox (but I leave 4.12.0-041200 installed for now). For my own record, the procedure I followed to install the 4.12.0-041200 was: wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/linux- headers-4.12.0-041200_4.12.0-041200.201707022031_all.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/linux- headers-4.12.0-041200-generic_4.12.0-041200.201707022031_amd64.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/linux- image-4.12.0-041200-generic_4.12.0-041200.201707022031_amd64.deb sha1sum *.deb # sums looked ok # as root (su -) from now on dpkg -i *.deb # ... # ERROR (dkms apport): kernel package linux-headers-4.12.0-041200-generic is not supported (twice) # ... # lots of W: Possible missing firmware /lib/firmware/nvidia/... But it did boot fine afterwards. (I did not attempt to remove or run virtualbox). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703091 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703091] Re: Kernel panic - not syncing: Fatal exception in interrupt
Sorry for the wrong bug category, but it was my 1st contact with "ubuntu-bug" command line tool, and I did not know which category to choose. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703091 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1703091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt
Ooops! My first contact with ubuntu-bug was a bit messy. I seem to have reported #1703091 Sorry for the mess. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702164 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1703091] [NEW] Kernel panic - not syncing: Fatal exception in interrupt
Public bug reported: I have a Clevo P150SM laptop. Recently, I have frequent kernel panics "Fatal exception in interrupt". Screenshot at https://i.stack.imgur.com/eZRcu.jpg (I will try to upload the screenshot of the console once I have a bug number). It happened the 1st time kernel 4.4.0-83 was installed and since yesterday's package updates was happening almost all the time. Today (the next morning) kernel 4.4.0-83 is booting fine. The symptons are simular to bug 1702164 (Sometimes it gets far enough to boot the X11 interface - and then crashes, Sometimes it crashes while still in console text mode). 2 leds are blinking: "CapsLock", and the other led which is not NumLock (but I don't know what it is). NumLock is not blinking. I alread did as root: apt clean apt install --reinstall linux-image-generic linux-image-4.4.0-83-generic update-initramfs -u -k 4.4.0-83-generic reboot but it stays the same. (The first time I upgraded to kernel 4.4.0-83 the power went down in the middle of the upgrade, and I fixed the problem more-or-less with the commands above.). When it crashes, I manage to boot in 4.4.0-81-generic, and it still seems to work fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.21 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Sat Jul 8 10:01:21 2017 InstallationDate: Installed on 2014-02-15 (1238 days ago) InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to xenial on 2016-10-29 (252 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade kernel-bug xenial ** Attachment added: "Screenshot of console crash on boot" https://bugs.launchpad.net/bugs/1703091/+attachment/4911198/+files/IMG_20170707_194006.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1703091 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1703091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt
Today, kernel 4.4.0-83 its booting fine (and it doesn't crash/hang on boot). (And yesterday, I did many reboots using the laptop power-on button, and it crashed every time, after the package upgrades). I run ubuntu-bug and chose "distribution upgrade" category (what else ?), but it gave back no bug report number, so that I can add an explanation to what is being reported. Next time it happens, I will try to follow https://wiki.ubuntu.com/Kernel/CrashdumpRecipe#Crash_kernel_fails_to_load:_Hang (but it seems a bit complicated). (and I will run a memory check first...) Thank you for the followup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702164 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt
Sorry if this not the proper way to ask, but I think I may have the same problem (with a Clevo P150SM laptop), and asked for help on https://askubuntu.com/questions/933015/ubuntu-16-04-kernel-4-4-0-83 -panic-fatal-exception-in-interrupt (For me, it started crashing again today after one more set of package updates). If you think I may have relevant information, please ask, and I will upload/post. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702164 Title: Kernel panic - not syncing: Fatal exception in interrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638420] Re: LVM install with Lubuntu fails due to missing lvm2 package
Hello everyone, i could solve the problem by using the alternate iso 16.10 and what it did different was to unmount a partition that was being used. Without unmonting it i could not install grub on the destination drive ever. Now all it is OK and i am using EFI. If you need me to do some other testing please say so. Cheers!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638420 Title: LVM install with Lubuntu fails due to missing lvm2 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638420/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699671] Re: installer crashes on this machine
OK i am adding the syslog now. Please if you need, contact me. I am available to help. All the best, good luck, Pedro ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1699671/+attachment/4900732/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699671 Title: installer crashes on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1699671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699671] [NEW] installer crashes on this machine
Public bug reported: I am trying to install Lubuntu 16.10 on this machine. Preferably with EFI secure boot options. It does not work. Upgraded BIOS and all firmware. Still didn't work. Tried to install normally with legacy BIOS settings still doesn't work. After every attempt i low-level formatted the SSD. I am available to solve this problem, please contact me at any time. If you want we can talk by skype. PS: i cannot seem to be able to attach both log files syslog and partman as you ask. But the problem seems to repeat itself. So i will send the partman wich seems to be more associated with not being able to instal grub2 ( happened always ). Thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.14 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CasperVersion: 1.379 Date: Thu Jun 22 05:05:58 2017 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=pt LiveMediaBuild: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lubuntu ubiquity-16.10.14 yakkety ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1699671/+attachment/4900724/+files/partman -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699671 Title: installer crashes on this machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1699671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1694214] [NEW] wget http://beta.unity3d.com/download/e348e673a4c6/unity-editor_amd64-5.6.0xf1Linux.deb -O unity-editor.deb
Public bug reported: dpkg: erro ao processar o arquivo unity-editor.deb (--install): impossível acessar arquivo: Arquivo ou diretório não encontrado Erros foram encontrados durante o processamento de: unity-editor.deb ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 225-1ubuntu9.1 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sun May 28 18:00:52 2017 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2015-12-06 (539 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: systemd Title: package systemd-sysv 225-1ubuntu9.1 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694214 Title: wget http://beta.unity3d.com/download/e348e673a4c6/unity- editor_amd64-5.6.0xf1Linux.deb -O unity-editor.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1694214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1674792] [NEW] package libkjsapi4 4:4.14.16-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkjsapi4 4:4.14.16-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-69.90-generic 4.4.52 Uname: Linux 4.4.0-69-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 21 18:22:45 2017 DuplicateSignature: package:libkjsapi4:4:4.14.16-0ubuntu3.1 Setting up libkdnssd4 (4:4.14.16-0ubuntu3.1) ... dpkg: error processing package libkjsapi4 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-07-12 (251 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: kde4libs Title: package libkjsapi4 4:4.14.16-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kde4libs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1674792 Title: package libkjsapi4 4:4.14.16-0ubuntu3.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/1674792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1633791] [NEW] package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: tzdata 2016g-0ubuntu0.16.04 ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21 Uname: Linux 4.4.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Oct 15 21:22:58 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-06-30 (107 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: tzdata Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1633791 Title: package tzdata 2016g-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1633791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594129] [NEW] package postgresql-9.4 (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
Public bug reported: I tried to uninstall and something went wrong. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: postgresql-9.4 (not installed) ProcVersionSignature: Ubuntu 4.2.0-38.45-generic 4.2.8-ckt10 Uname: Linux 4.2.0-38-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 AptOrdering: postgresql-contrib-9.4: Purge postgresql-9.4: Purge NULL: ConfigurePending Architecture: amd64 Date: Sun Jun 19 12:44:29 2016 DuplicateSignature: package:postgresql-9.4:(not installed):subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2015-08-13 (311 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu3 SourcePackage: postgresql-9.4 Title: package postgresql-9.4 (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: Upgraded to wily on 2015-11-17 (214 days ago) ** Affects: postgresql-9.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check wily -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1594129 Title: package postgresql-9.4 (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postgresql-9.4/+bug/1594129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571903] [NEW] PAM gets stuck waiting for audit_log_acct_message()
Public bug reported: During PAM processing of any request (auth, acct, or session), the function audit_log_acct_message () (from /lib/i386-linux- gnu/libaudit.so.1 ) is called to audit the event. One of the variables that can be used during audit logging is the hostname of the requester (PAM_RHOST). The audit_log_acct_message () function try to resolve this hostname if the address is still not known, but when the DNS server is not reachable or the query return is SERVFAIL, system tries a couple of times before aborting the process of name resolution, which leads to time wasted by PAM waiting for the return of audit_log_acct_message (). In some cases, this time wasting causes the requester application to timeout, for example a VPN user. This issue happened to me while testing a vpn solution using pppd, and at the same time dns server was down. The vpn client was timing out during user/pass verification phase, and by looking at pppd debug logs it was because of a very slow PAM processing. At same time, I could see server was sending strange dns queries about "ppp0". (pppd includes the dynamic interface name as the PAM_RHOST when calling PAM). Summary of events: 1-pppd passes user/pass to PAM for auth 2-PAM pocess auth 3-PAM audit the event <- time wasted waiting for dns (>5 seconds) (...)->the process is repeated for PAM acct and session checks. By the way if DNS server responds with NXDOMAIN, the resolver aborts immediately and the stuck issue is not seen. This I think is what happens on most cases. I wonder if PAM can be improved by making a non-blocking call to audit_log_acct_message (). Packages: libpam0g:i386 - 1.1.8-1ubuntu2.2 libaudit1:i386 - 1:2.3.2-2ubuntu1 # lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 Backtrace attached using pppd example. ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: blocking dns gethostbyname pam pppd query stuck ** Attachment added: "backtrace_pppd_gethostbyname.txt" https://bugs.launchpad.net/bugs/1571903/+attachment/4639556/+files/backtrace_pppd_gethostbyname.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571903 Title: PAM gets stuck waiting for audit_log_acct_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1571903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571889] [NEW] pppd exits with Fatal signal 11, on PAM auth.
Public bug reported: The crash occurs if the following PAM auth line is present when pppd tries to authenticate a user ("login" option) authoptionalpam_smbpass.so migrate Apr 18 23:40:39 ubuntu pppd[1622]: Initializing PAM (3) for user j Apr 18 23:40:39 ubuntu pppd[1622]: ---> PAM INIT Result = 0 Apr 18 23:40:39 ubuntu pppd[1622]: Attempting PAM authentication Apr 18 23:40:39 ubuntu pppd[1622]: Fatal signal 11 Apr 18 23:40:39 ubuntu charon: 16[KNL] interface ppp0 deleted This is seen at least on the following scenario: 1-L2TP vpn environment using xl2tpd + pppd 2-authentication method is PAP. 3-ppp version 2.4.5-5.1ubuntu2.2 The PAM config auth line is automatically added to "common-auth" when installing the following package libpam-smbpass:i386 2:4.1.6+dfsg-1ubuntu2 # lsb_release -rd Description:Ubuntu 14.04.4 LTS Release:14.04 ** Affects: ppp (Ubuntu) Importance: Undecided Status: New ** Tags: libpam-smbpass pam pppd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571889 Title: pppd exits with Fatal signal 11, on PAM auth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1571889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563184] Re: InitializeSandbox() called with multiple threads in process gpu-process
Problem also exists in archlinux arm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563184 Title: InitializeSandbox() called with multiple threads in process gpu- process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [ubuntu-studio-users] [solved] Jack can´t start
I agree with you, it will be difficult to me, if it was so difficult to "see" the second button and looks like is working really well until now. Thanks again Best regards, JB On 30 Mar 2016 7:37 p.m., "Ralf Mardorf"wrote: > The new qjackctl GUI only provides one button. It will be available for > the next release: http://packages.ubuntu.com/xenial/qjackctl > > I have it installed for my Arch Linux. > > [rocketmouse@archlinux ~]$ pacman -Q qjackctl > qjackctl 0.4.1-2 > > It's already possible to compile it for Wily and it works even with > Qt5 already, but the repositories still provide the old GUI. > > [root@moonstudio ~]# lsb_release -rc;dpkg -l qjackctl|grep ii > Release:15.10 > Codename: wily > ii qjackctl 0.4.0-29-g45508a354d-1 amd64JACK Audio > Connection Kit Qt GUI Interface. > > At the moment I only have access to the command line of my Ubuntu > install, since I run it in a systemd-nspawn containmer, so I don't know > if there is already just one button for 0.4.0, however, Xenial will > provide 0.4.1 too and most likely it can be compiled for Wily. > > I dislike that "Most advanced Setup/Settings are moved into new > Setup/Advanced settings tab" [1], but seemingly the removed button > seems to be an advantage for newbies. > > [1] http://qjackctl.sourceforge.net/qjackctl-downloads.html > > Anyway, I recommend to stay with the current version, since it now > works for you and building it for Wily might not be that easy for a > beginner. > > Regards, > Ralf > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
looks like now is working well, should be that change of buttons on the interface, now i used the one on the right and starts by itself working well, without start in jackd in terminal. To be honest never noticed that button before.. Thank you very much, JB PS- i will make several trials and if still working good i will put as solved. On Wed, Mar 30, 2016 at 3:44 PM, Joao Bruno <joaobrunogalhe...@gmail.com> wrote: > Ok, I will do it. Just to be more precise, QjackCtl only works after I > run jackd from terminal and after run a software, I'm using ardour, if I > run QjackCtl before open ardour it fails and send me the usual failure > message. > On 30 Mar 2016 5:36 p.m., "Kaj Ailomaa" <zeque...@mousike.me> wrote: > >> On Wed, Mar 30, 2016, at 04:33 PM, Kaj Ailomaa wrote: >> > On Wed, Mar 30, 2016, at 04:10 PM, Joao Bruno wrote: >> > > In this case I put default, but I also did it with the both devices >> that >> > > appears, hw:0 or plughw:0, doesn't work as well. At this moment I >> started >> > > jackd by the terminal and after opened the QjackCtl and looks like is >> > > working correctly, with the settings as default. >> > > >> > > Thank you, it was by your advice that jackd was working by terminal >> that >> > > I >> > > did this way, at least is working, not by the regular way but is >> > > working. >> > > >> > > Thank you very much, JB >> > > >> > default means hw:0. Better to choose the correct device in "Interface", >> > rather than default. Why? Because each time you boot your computer, the >> > device may be in a different order. >> > >> > Again, under "Interface", select the correct device, the start jack. >> >> btw, there are two buttons next to "Interface". Confusing, I know. It is >> the one to the right you should use, no the one to the left. >> >> -- >> ubuntu-studio-users mailing list >> ubuntu-studio-users@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users >> > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
In this case I put default, but I also did it with the both devices that appears, hw:0 or plughw:0, doesn't work as well. At this moment I started jackd by the terminal and after opened the QjackCtl and looks like is working correctly, with the settings as default. Thank you, it was by your advice that jackd was working by terminal that I did this way, at least is working, not by the regular way but is working. Thank you very much, JB PS- not completely solved but working On 30 Mar 2016 5:01 p.m., "Kaj Ailomaa" <zeque...@mousike.me> wrote: > On Wed, Mar 30, 2016, at 03:04 PM, Joao Bruno wrote: > > http://picpaste.com/Screenshot_-_30-03-2016_-_13_50_29-GwYDHNJW.png > > > > In the picture above you have not selected a device. If you select the > correct one, jack will start. > > Select the device from "Interface". > > If you absolutely want to use your hdmi output, instead of the analog > one, you need to set "Audio: duplex" to outputs only. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
http://picpaste.com/Screenshot_-_30-03-2016_-_13_50_29-GwYDHNJW.png http://picpaste.com/Screenshot_-_30-03-2016_-_13_50_54-6czeHw60.png http://picpaste.com/Screenshot_-_30-03-2016_-_13_51_15-sDjm1Klu.png http://picpaste.com/Screenshot_-_30-03-2016_-_13_51_36-jXwHfFgv.png On Tue, Mar 29, 2016 at 5:09 PM, Ralf Mardorfwrote: > >Oops, http://picpaste.com/ or similar. > > ".de" was not the first typo today :D, I already confused jackd with > qjackctl settings and bad phrased at least an explanation regarding > MIDI, that in this context is irrelevant. However, as Kaj already > pointed out, it most likely is an issue with your qjackctl settings, > that makes jackdbus (and jackd) fail to start. When you launched > jackd from command line it did run. > > By screenshots we most likely will find the culprit. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
I'm not sure of course, but I think should be something between jack and pulse audio, missing divers maybe. I will try everything I can. I can always reinstall the sistem. Thank you, JB On 29 Mar 2016 6:49 p.m., "Ralf Mardorf" <ralf.mard...@alice-dsl.net> wrote: > On Tue, 2016-03-29 at 16:37 +0100, Joao Bruno wrote: > > this the jack version > > jb@jb-SATELLITE-L50-B:~$ pulseaudio --kill > > jb@jb-SATELLITE-L50-B:~$ jackd -dalsa -dhw:1 -r48000 -p1024 -n3 > > jackdmp 1.9.10 > > Copyright 2001-2005 Paul Davis and others. > > Copyright 2004-2013 Grame. > > jackdmp comes with ABSOLUTELY NO WARRANTY > > This is free software, and you are welcome to redistribute it > > under certain conditions; see the file COPYING for details > > no message buffer overruns > > no message buffer overruns > > no message buffer overruns > > JACK server starting in realtime mode with priority 10 > > audio_reservation_init > > Acquire audio card Audio1 > > creating alsa driver ... hw:1|hw:1|1024|3|48000|0|0|nomon|swmeter|- > > |32bit > > configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 3 > > periods > > ALSA: final selected sample format for capture: 32bit integer little- > > endian > > ALSA: use 3 periods for capture > > ALSA: final selected sample format for playback: 32bit integer little- > > endian > > ALSA: use 3 periods for playback > > If you now would start qjackctl, while jackd still runs in the terminal, > it would work. > > > this is the message after i did your orientations > > No, you most likely didn't continue running jackd in the terminal, when > launching qjackctl. > > > [snip] > > /dev/audio|/dev/audio|1024|3|44100|0|0|nomon|swmeter|-|32bit >^ >^ > Qjackctl does use different settings, instead of 48000 used by the > terminal and qjackctl by default doesn't kill a running instance of > jackd, it does use it, as long as there is no bug or a script is started > by the jackd settings. In qjackctl's settings ensure that in "Options" > "Execute script at startup" is unchecked, disabled. > > > ALSA lib control.c:953:(snd_ctl_open_noupdate) Invalid CTL /dev/audio > > control open "/dev/audio" (No such file or directory) > > ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM /dev/audio > > ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM /dev/audio > > ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to > > capture-only mode > > Cannot initialize driver > > JackServer::Open failed with -1 > > Failed to open server > > 16:36:09.369 JACK was stopped with exit status=255. > > [snip] > > Your qjackctl settings are bad, and/or qjackctl is buggy and or some > pulseaudio-jack-thingy still gets started. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
this the jack version jb@jb-SATELLITE-L50-B:~$ pulseaudio --kill jb@jb-SATELLITE-L50-B:~$ jackd -dalsa -dhw:1 -r48000 -p1024 -n3 jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2013 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details no message buffer overruns no message buffer overruns no message buffer overruns JACK server starting in realtime mode with priority 10 audio_reservation_init Acquire audio card Audio1 creating alsa driver ... hw:1|hw:1|1024|3|48000|0|0|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 3 periods ALSA: final selected sample format for capture: 32bit integer little-endian ALSA: use 3 periods for capture ALSA: final selected sample format for playback: 32bit integer little-endian ALSA: use 3 periods for playback this is the message after i did your orientations under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 ALSA lib control.c:953:(snd_ctl_open_noupdate) Invalid CTL /dev/audio control open "/dev/audio" (No such file or directory) ALSA lib control.c:953:(snd_ctl_open_noupdate) Invalid CTL /dev/audio control open "/dev/audio" (No such file or directory) creating alsa driver ... /dev/audio|/dev/audio|1024|3|44100|0|0|nomon|swmeter|-|32bit ALSA lib control.c:953:(snd_ctl_open_noupdate) Invalid CTL /dev/audio control open "/dev/audio" (No such file or directory) ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM /dev/audio ALSA lib pcm.c:2239:(snd_pcm_open_noupdate) Unknown PCM /dev/audio ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode Cannot initialize driver JackServer::Open failed with -1 Failed to open server 16:36:09.369 JACK was stopped with exit status=255. 16:36:11.435 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started On Tue, Mar 29, 2016 at 4:26 PM, Ralf Mardorfwrote: > Please temporarily stop pulseaudio, since I don't have pulseaudio > installed and I never used it, I'm not sure how to do this, but I guess > running > > pulseaudio --kill > > does the job nowadays, after that run > > qjackctl > > and in "Settings... > Misc" uncheck "Enable D-Bus interface", then > start and stop and close qjackctl, ignore error messages when starting, > I only want to ensure, that D-Bus is disabled by the settings, what ever > version of qjackctl you are using. > > In a terminal run > > jackd -dalsa -dhw:1 -r48000 -p1024 -n3 > > and assumed it shouldn't work run > > jackd -dalsa -dhw:0 -r48000 -p1024 -n3 > > Normally it's better to use "-n2" and go lower than "-p1024", but for > testing purpose "-p1024 -n3" are good values. > > After starting jackd in a terminal, you can start qjackctl. > > Does this work? > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] [solved] can´t mount hard drive of ntfs [solved]
On Tue, Mar 29, 2016 at 3:20 PM, Ralf Mardorf <ralf.mard...@alice-dsl.net> wrote: > On Tue, 29 Mar 2016 15:13:20 +0100, Joao Bruno wrote: > >Problem solved. > >I would not expected that when i shutdown, the windows don´t shutdown > >completely! > > > >Thank you very much. > > You are welcome! > > I didn't know this either, but the output message of the mount command > made it easy to use a search engine and to find out, how to solve the > issue. > > Regards, > Ralf > > PS: Please consider to follow the fist sentence on the page were you > subscribed, > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users, it's > > "Please read community.ubuntu.com/contribute/support/mailinglists/ [1] > about mailing etiquette." > > It makes it easier for the community to help you. > > In addition, it's common practise to mark the subject as "[solved]", so > other users with the same issue could easier find a solution. > > [1] http://community.ubuntu.com/contribute/support/mailinglists/ > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
have this message , i don`t know if helps : 6:07:49.705 Patchbay deactivated. 16:07:49.708 Statistics reset. 16:07:49.713 ALSA connection change. 16:07:49.718 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started 16:07:49.724 ALSA connection graph change. (qjackctl:2533): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2533): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed On Tue, Mar 29, 2016 at 4:05 PM, Joao Bruno <joaobrunogalhe...@gmail.com> wrote: > that´s what i did, stills not working. > i tried again to be sure, tried with all the options > > On Tue, Mar 29, 2016 at 3:31 PM, Ralf Mardorf <ralf.mard...@alice-dsl.net> > wrote: > >> On Tue, 29 Mar 2016 16:16:13 +0200, Kaj Ailomaa wrote: >> >I'm pretty confident it still comes down to selecting the proper device >> >for jack, and not messing up other settings, like having separate >> >improper settings for in/out. >> >> If the original poster shouldn't know how to chose the correct device by >> qjackctl's settings, then we need to know the output of >> >> qjackctl -v >> >> since we need to know, if the settings GUI is the old or the new one. >> resp. since it's a default install of what ever version of Ubuntu >> Studio, it most likely is the old GUI. >> >> I don't have the old GUI available, but I suspect that there are >> >> "Interface" >> "Output device" >> "Input device" >> >> available by Qjackctl's old GUI's "Setup...". >> >> If so, than nothing should be messed up, assumed the original poster >> would select the same device for "Interface", "Output device" and "Input >> device". However, just one of the two devices could work in "duplex" >> mode. >> >> -- >> ubuntu-studio-users mailing list >> ubuntu-studio-users@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users >> > > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
that´s what i did, stills not working. i tried again to be sure, tried with all the options On Tue, Mar 29, 2016 at 3:31 PM, Ralf Mardorfwrote: > On Tue, 29 Mar 2016 16:16:13 +0200, Kaj Ailomaa wrote: > >I'm pretty confident it still comes down to selecting the proper device > >for jack, and not messing up other settings, like having separate > >improper settings for in/out. > > If the original poster shouldn't know how to chose the correct device by > qjackctl's settings, then we need to know the output of > > qjackctl -v > > since we need to know, if the settings GUI is the old or the new one. > resp. since it's a default install of what ever version of Ubuntu > Studio, it most likely is the old GUI. > > I don't have the old GUI available, but I suspect that there are > > "Interface" > "Output device" > "Input device" > > available by Qjackctl's old GUI's "Setup...". > > If so, than nothing should be messed up, assumed the original poster > would select the same device for "Interface", "Output device" and "Input > device". However, just one of the two devices could work in "duplex" > mode. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
iḿ trying that, and avoid mess with in/out, but stills not working, if i read correctly On Tue, Mar 29, 2016 at 3:16 PM, Kaj Ailomaa <zeque...@mousike.me> wrote: > On Tue, Mar 29, 2016, at 04:11 PM, Ralf Mardorf wrote: > > On Tue, 29 Mar 2016 15:03:31 +0100, Joao Bruno wrote: > > >Happens the same > > > > I searched this way (but with startpage instead of google): > > > > https://www.google.de/#q=linux+driver+HDA+Intel+PCH+CX20756 > > > > It leads to: > > > > http://docs.slackware.com/howtos:hardware:audio_and_snd-hda-intel > > > > This might help you to figure out what options to use. > > > > I'm pretty confident it still comes down to selecting the proper device > for jack, and not messing up other settings, like having separate > improper settings for in/out. So, my initial answer already had all the > essential information - if one reads carefully enough. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
I will try and give you a answer. Thank you very much. Best regards, JB On Tue, Mar 29, 2016 at 3:11 PM, Ralf Mardorf <ralf.mard...@alice-dsl.net> wrote: > On Tue, 29 Mar 2016 15:03:31 +0100, Joao Bruno wrote: > >Happens the same > > I searched this way (but with startpage instead of google): > > https://www.google.de/#q=linux+driver+HDA+Intel+PCH+CX20756 > > It leads to: > > http://docs.slackware.com/howtos:hardware:audio_and_snd-hda-intel > > This might help you to figure out what options to use. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] can´t mount hard drive of ntfs
Problem solved. I would not expected that when i shutdown, the windows don´t shutdown completely! Thank you very much. Best regards , JB On Tue, Mar 29, 2016 at 2:58 PM, Joao Bruno <joaobrunogalhe...@gmail.com> wrote: > No, just the usual shutdown, You ask if i know the difference between, i > never expect that it needs special movements for a thing that should be > what it is. > I am not a expert, thatś why i ask for help. > I will try and give you a answer. > thanks > > On Tue, Mar 29, 2016 at 2:45 PM, Ralf Mardorf <ralf.mard...@alice-dsl.net> > wrote: > >> On Tue, 29 Mar 2016 14:39:22 +0100, Joao Bruno wrote: >> >Really?! >> >> I don't use Windows 10, but around 10 seconds of Internet research lead >> to >> >> http://superuser.com/questions/880867/cannot-mount-ntfs-partitions-because-of-windows-10 >> : >> >> "You have to do a full shutdown in Windows 10, by pressing the SHIFT >> key + clicking on shutdown." >> >> You really did this? >> >> -- >> ubuntu-studio-users mailing list >> ubuntu-studio-users@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users >> > > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
Happens the same On 29 Mar 2016 5:01 p.m., "Ralf Mardorf" <ralf.mard...@alice-dsl.net> wrote: > On Tue, 29 Mar 2016 14:50:35 +0100, Joao Bruno wrote: > >card 1: PCH [HDA Intel PCH], device 0: CX20756 Analog [CX20756 Analog] > > Subdevices: 1/1 > > Subdevice #0: subdevice #0 > > > List of CAPTURE Hardware Devices > >card 1: PCH [HDA Intel PCH], device 0: CX20756 Analog [CX20756 Analog] > > Subdevices: 1/1 > > Subdevice #0: subdevice #0 > > Only this card could be used in duplex mode, the other card is playback > only. Actually I don't understand "Cannot open PCM device alsa_pcm for > playback", I would expect that no device for "capture", aka "record" aka > "input" could be opened. I suspect that the HDMI devcie is part of > the graphics and suffers from a broken driver. > > What qjackctl output do you get if you chose "hw:1"? > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] can´t mount hard drive of ntfs
No, just the usual shutdown, You ask if i know the difference between, i never expect that it needs special movements for a thing that should be what it is. I am not a expert, thatś why i ask for help. I will try and give you a answer. thanks On Tue, Mar 29, 2016 at 2:45 PM, Ralf Mardorf <ralf.mard...@alice-dsl.net> wrote: > On Tue, 29 Mar 2016 14:39:22 +0100, Joao Bruno wrote: > >Really?! > > I don't use Windows 10, but around 10 seconds of Internet research lead > to > > http://superuser.com/questions/880867/cannot-mount-ntfs-partitions-because-of-windows-10 > : > > "You have to do a full shutdown in Windows 10, by pressing the SHIFT > key + clicking on shutdown." > > You really did this? > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
when i run aplay -l;printf "\n###\n\n";arecord -l;printf "\n###\n\n";amidi -l appears this * List of PLAYBACK Hardware Devices card 0: HDMI [HDA Intel HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA Intel HDMI], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: PCH [HDA Intel PCH], device 0: CX20756 Analog [CX20756 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ### List of CAPTURE Hardware Devices card 1: PCH [HDA Intel PCH], device 0: CX20756 Analog [CX20756 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 On Tue, Mar 29, 2016 at 2:43 PM, Ralf Mardorf <ralf.mard...@alice-dsl.net> wrote: > On Tue, 29 Mar 2016 14:34:22 +0100, Joao Bruno wrote: > >I will try, I already chose all the options devices and still not > >working, something with d-bus, can't connect to server. > > Actually we still refer too > "Cannot open PCM device alsa_pcm for playback." > if you get different output for other devices, post the output. > However, most important is the output of >aplay -l;printf "\n###\n\n";arecord -l;printf "\n###\n\n";amidi -l > at the moment. > > Please, don't top post, don't quote emails in full, don't use multipart > with HTML, instead inline or bottom post, onoly quote relevant text and > send emails in plain text. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] can´t mount hard drive of ntfs
Really?! On 29 Mar 2016 4:38 p.m., "Joao Bruno" <joaobrunogalhe...@gmail.com> wrote: > I really shutdown windows, since the first time, do you think should be > some drivers missing? > On 29 Mar 2016 4:33 p.m., "Ralf Mardorf" <ralf.mard...@alice-dsl.net> > wrote: > >> On Tue, 29 Mar 2016 14:12:10 +0100, Joao Bruno wrote: >> >I was my first option, but doesn't work. >> >> You need to boot Windows and instead of hibernate, you need to shut >> down windows, then you likely can mount it by your Linux install. Is >> this what you already did? Imagine what would happen, if a hibernated >> state should get started, while in the meantime a used partition >> changed it's state. >> >> -- >> ubuntu-studio-users mailing list >> ubuntu-studio-users@lists.ubuntu.com >> Modify settings or unsubscribe at: >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users >> > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] can´t mount hard drive of ntfs
I really shutdown windows, since the first time, do you think should be some drivers missing? On 29 Mar 2016 4:33 p.m., "Ralf Mardorf" <ralf.mard...@alice-dsl.net> wrote: > On Tue, 29 Mar 2016 14:12:10 +0100, Joao Bruno wrote: > >I was my first option, but doesn't work. > > You need to boot Windows and instead of hibernate, you need to shut > down windows, then you likely can mount it by your Linux install. Is > this what you already did? Imagine what would happen, if a hibernated > state should get started, while in the meantime a used partition > changed it's state. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
I will try, I already chose all the options devices and still not working, something with d-bus, can't connect to server. On 29 Mar 2016 4:28 p.m., "Ralf Mardorf"wrote: > On Tue, 29 Mar 2016 15:10:44 +0200, Kaj Ailomaa wrote: > >I couldn't spot any clues from the error message. > > Regarding > > "Tue Mar 29 13:07:39 2016: creating alsa driver ... > hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit > > Tue Mar 29 13:07:39 2016: ERROR: ALSA: Cannot open PCM device alsa_pcm > for playback. Falling back to capture-only mode" > > I recommend to open a terminal and to run > > aplay -l;printf "\n###\n\n";arecord -l;printf "\n###\n\n";amidi -l > > then the original poster should select the output, right click, chose > copy and paste it to an email, to send it to the mailing list. > > Perhaps the original poster has several audio devices and maybe at least > one device might provide record ports only or just midi ports. Since the > order of cards could change with each reboot, it requires either to > edit /etc/modprobe.d/alsa-base.conf, for example > > $ cat /etc/modprobe.d/alsa-base.conf > # ALSA module ordering > options snd slots=snd_hdspm,snd_ice1712,snd_ice1712 > > or instead of choosing "hw:0" to chose an audio device by it's > dedicated name. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] can´t mount hard drive of ntfs
I shutdown windows, and stills the problem, I don't know about it, but looks like, it's a problem that comes with the 64 bits versions, in the earlier versions I didn't have any problems... Thanks, JB On 29 Mar 2016 4:22 p.m., "Kaj Ailomaa" <zeque...@mousike.me> wrote: > On Tue, Mar 29, 2016, at 03:12 PM, Joao Bruno wrote: > > I was my first option, but doesn't work. > > Thanks > > On 29 Mar 2016 4:07 p.m., "Kaj Ailomaa" <zeque...@mousike.me> wrote: > > > > What do you mean? Did you boot Windows and actually make it shutdown > instead of just hibernate? > Besides, problem solving Windows is out of the scope for this mail list. > > > > On Tue, Mar 29, 2016, at 02:41 PM, Joao Bruno wrote: > > > > when i try to mount the harda drive in ntfs of windows, don´t mount. > > > > Iḿ using windows 10 and ubuntu studio 14. the message that appears > it´s > > > > this: > > > > > > > > Error mounting /dev/sda4 at /media/jb/TI31418400A: Command-line > `mount -t > > > > "ntfs" -o > > > > > "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" > > > > "/dev/sda4" "/media/jb/TI31418400A"' exited with non-zero exit > status 14: > > > > Windows is hibernated, refused to mount. > > > > > > I believe the answer to your question is in the error message "Windows > > > is hibernated, refused to mount." > > > > > > -- > > > ubuntu-studio-users mailing list > > > ubuntu-studio-users@lists.ubuntu.com > > > Modify settings or unsubscribe at: > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > > > > > -- > > ubuntu-studio-users mailing list > > ubuntu-studio-users@lists.ubuntu.com > > Modify settings or unsubscribe at: > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] Jack can´t start
I am with original set up, fresh installation, looks like I have some conflict between also,Jack and pulseaudio. Thanks, JB On 29 Mar 2016 4:11 p.m., "Kaj Ailomaa" <zeque...@mousike.me> wrote: > > > On Tue, Mar 29, 2016, at 02:36 PM, Joao Bruno wrote: > > when i try to start jack , came this notification on jack messages, i > > don´t > > know what i can do... > > > (snip) > > I couldn't spot any clues from the error message. Reboot the computer, > so we are sure you have started out fresh. Launch qjackctl. Before > starting jack make sure you have selected the device you want to use. > Then, click "Start". > > If you have changed the system somehow, by adding PPAs, or installing > jackd1, or you have configured your jack settings in an improper way, > the method above might not work. Also, using HDMI output may not work. > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [ubuntu-studio-users] can´t mount hard drive of ntfs
I was my first option, but doesn't work. Thanks On 29 Mar 2016 4:07 p.m., "Kaj Ailomaa" <zeque...@mousike.me> wrote: > On Tue, Mar 29, 2016, at 02:41 PM, Joao Bruno wrote: > > when i try to mount the harda drive in ntfs of windows, don´t mount. > > Iḿ using windows 10 and ubuntu studio 14. the message that appears it´s > > this: > > > > Error mounting /dev/sda4 at /media/jb/TI31418400A: Command-line `mount -t > > "ntfs" -o > > "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" > > "/dev/sda4" "/media/jb/TI31418400A"' exited with non-zero exit status 14: > > Windows is hibernated, refused to mount. > > I believe the answer to your question is in the error message "Windows > is hibernated, refused to mount." > > -- > ubuntu-studio-users mailing list > ubuntu-studio-users@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users > -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
[ubuntu-studio-users] can´t mount hard drive of ntfs
when i try to mount the harda drive in ntfs of windows, don´t mount. Iḿ using windows 10 and ubuntu studio 14. the message that appears it´s this: Error mounting /dev/sda4 at /media/jb/TI31418400A: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sda4" "/media/jb/TI31418400A"' exited with non-zero exit status 14: Windows is hibernated, refused to mount. Failed to mount '/dev/sda4': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option. Thank you, JB -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
[ubuntu-studio-users] Jack can´t start
when i try to start jack , came this notification on jack messages, i don´t know what i can do... 3:07:35.586 Patchbay deactivated. 13:07:35.609 Statistics reset. 13:07:35.663 ALSA connection change. 13:07:36.296 D-BUS: Service is available (org.jackaudio.service aka jackdbus). Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started 13:07:36.302 ALSA connection graph change. (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed 13:07:39.298 D-BUS: JACK server could not be started. Sorry Tue Mar 29 13:07:39 2016: Starting jack server... Tue Mar 29 13:07:39 2016: JACK server starting in realtime mode with priority 10 Tue Mar 29 13:07:39 2016: Acquired audio card Audio0 Tue Mar 29 13:07:39 2016: creating alsa driver ... hw:0|hw:0|1024|2|44100|0|0|nomon|swmeter|-|32bit Tue Mar 29 13:07:39 2016: ERROR: ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode Tue Mar 29 13:07:39 2016: ERROR: Cannot initialize driver Tue Mar 29 13:07:39 2016: ERROR: JackServer::Open failed with -1 Tue Mar 29 13:07:39 2016: ERROR: Failed to open server Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed Tue Mar 29 13:07:41 2016: Saving settings to "/home/jb/.config/jack/conf.xml" ... 13:07:43.554 Could not connect to JACK server as client. - Overall operation failed. - Unable to connect to server. Please check the messages window for more info. Cannot connect to server socket err = No such file or directory Cannot connect to server request channel jack server is not running or cannot be started (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed (qjackctl:2281): Gtk-CRITICAL **: IA__gtk_widget_get_direction: assertion 'GTK_IS_WIDGET (widget)' failed Thank you, JB -- ubuntu-studio-users mailing list ubuntu-studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: [U-co] Ayuda. ¡Kernel panic! Error con paquete bcmwl
Sigo con el problema. Una vez conecta a internet por el wifi, se congela el sistema. El 5 de enero de 2016, 4:39, Alexander Bejarano Hincapié <abhi...@yahoo.es> escribió: > hola... > Segun launchpad esto ya está arreglado en la version This bug was fixed > in the package bcmwl - 6.30.223.248+bdcom-0ubuntu4.1 > > --- > Sent from my Ubuntu Linux > > Alexander Bejarano Hincapié > Linux User #390516 - http://counter.li.org/ > Universidad Distrital - Francisco José de Caldas - Bogotá, Colombia - > http://ieee.udistrital.edu.co > > > From: Joao Patiño <edsonjoa...@gmail.com> > To: Ubuntu Colombia <ubuntu-co@lists.ubuntu.com> > Sent: Saturday, 26 December 2015, 17:36 > Subject: [U-co] Ayuda. ¡Kernel panic! Error con paquete bcmwl > > OS: Ubuntu 14.04.3 > Arq: x86 > > Actualicé paquetes hace un par de días usando el gestor predeterminado (no > synaptic) y tras el reinicio e inicio de sesión se congeló. Probé una vez > más y tras inicio de sesión inmediatamente abrí tty y pude ver que era un > kernel panic lo que congelaba el sistema, más específicamente por problemas > con el controlador de red wifi. > > En si, puedo usar el laptop si desactivo wifi y solo uso internet por cable > pero una vez que intento usar el wifi para conectarme a internet se genera > el error. > > Tampoco sirvió actualizar al último kernel (4.x.x) o usar uno anterior > (3.19.24). Parece ser un bug confirmado, según entendí. > > https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880 > https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1453365 > > #Ayuda > ¿Ahora qué procede? > -- > Al escribir recuerde observar la etiqueta (normas) de esta lista: > http://goo.gl/Pu0ke > Para cambiar su inscripción, vaya a "Cambio de opciones" en > http://goo.gl/Nevnx > > > -- > Al escribir recuerde observar la etiqueta (normas) de esta lista: > http://goo.gl/Pu0ke > Para cambiar su inscripción, vaya a "Cambio de opciones" en > http://goo.gl/Nevnx > -- Al escribir recuerde observar la etiqueta (normas) de esta lista: http://goo.gl/Pu0ke Para cambiar su inscripción, vaya a "Cambio de opciones" en http://goo.gl/Nevnx
[U-co] Ayuda. ¡Kernel panic! Error con paquete bcmwl
OS: Ubuntu 14.04.3 Arq: x86 Actualicé paquetes hace un par de días usando el gestor predeterminado (no synaptic) y tras el reinicio e inicio de sesión se congeló. Probé una vez más y tras inicio de sesión inmediatamente abrí tty y pude ver que era un kernel panic lo que congelaba el sistema, más específicamente por problemas con el controlador de red wifi. En si, puedo usar el laptop si desactivo wifi y solo uso internet por cable pero una vez que intento usar el wifi para conectarme a internet se genera el error. Tampoco sirvió actualizar al último kernel (4.x.x) o usar uno anterior (3.19.24). Parece ser un bug confirmado, según entendí. https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1415880 https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1453365 #Ayuda ¿Ahora qué procede? -- Al escribir recuerde observar la etiqueta (normas) de esta lista: http://goo.gl/Pu0ke Para cambiar su inscripción, vaya a "Cambio de opciones" en http://goo.gl/Nevnx
[Bug 1509769] Re: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Same happened to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1509769 Title: package initramfs-tools 0.120ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1472601] [NEW] grub2 failed to install during fresh installation
Public bug reported: During a fresh install, grub-installer doesn't complete grbu2 install. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubiquity 2.18.8.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CasperVersion: 1.340 Date: Wed Jul 8 09:27:36 2015 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed cdrom-detect/try-usb=true noprompt floppy.allowed_drive_mask=0 ignore_uuid boot=casper only-ubiquity quiet splash -- LiveMediaBuild: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) ProcEnviron: LANGUAGE=pt_BR.UTF-8 TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=pt_BR.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 trusty ubiquity-2.18.8.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1472601 Title: grub2 failed to install during fresh installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1472601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451613] Re: Unity/compiz crashes when locking screen
I am also having the same problem here, it started to happen a lot after I did regular updates last friday. I am using nvidia drivers 331.113 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451613 Title: Unity/compiz crashes when locking screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1451613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1401606] [NEW] xorg crashes with no likely cause after automatic nvidia 331.113update 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build
Public bug reported: automatic update to nvidia driver (from 331.xx-update driver version available under hardware prorietary drivers menu to further 331.113update) causes frequent xorg crashes with no apparent cause, unrelated to any particular process. Also gdm fails to load on boot-up\reboot frequently. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331-updates 331.113-0ubuntu0.0.4 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 DKMSKernelVersion: 3.13.0-43-generic Date: Thu Dec 11 13:02:55 2014 InstallationDate: Installed on 2014-12-03 (8 days ago) InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140723) PackageVersion: 331.113-0ubuntu0.0.4 SourcePackage: nvidia-graphics-drivers-331-updates Title: nvidia-331-updates 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1401606 Title: xorg crashes with no likely cause after automatic nvidia 331.113update 331.113-0ubuntu0.0.4: nvidia-331-updates kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1401606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1380671] [NEW] machinedots is wrong and not all processes killed on stop
Public bug reported: Hi guys the init file configuration is wrong /etc/init.d/hobbit-client: [ -z $MACHINEDOTS ] MACHINEDOTS=`hostname -f` this is searching for a variable not set and then sets the machine name using hostname -f should be: MACHINEDOTS The hostname of the local system. Default: Taken from uname -n. https://www.xymon.com/xymon/help/manpages/man5/xymonclient.cfg.5.html the reason is that uname -n takes only the name part of hostname and hostname -f takes the fqdn I've also noticed that every time the init script gets executed it doesn't kill all the processes, there is trash left behind hobbit 19162 0.0 0.0 4400 612 ?S15:53 0:00 sh -c vmstat 300 2 1/var/lib/hobbit/tmp/hobbit_vmstat.hostname-19132 21; mv /var/lib/hobbit/tmp/hobbit_vmstat.ISSV-hostname /var/lib/hobbit/tmp/hobbit_vmstat.hostname hobbit 19164 0.0 0.0 6508 516 ?S15:53 0:00 \_ vmstat 300 2 hobbit 19233 0.0 0.0 4400 616 ?S15:53 0:00 sh -c vmstat 300 2 1/var/lib/hobbit/tmp/hobbit_vmstat.hhostname 21; mv /var/lib/hobbit/tmp/hobbit_vmstat.hhostname /var/lib/hobbit/tmp/hobbit_vmstat.hostname hobbit 19235 0.0 0.0 6508 516 ?S15:53 0:00 \_ vmstat 300 2 hobbit 19831 0.0 0.0 8608 680 ?Ss 15:54 0:00 /usr/lib/hobbit/client/bin/hobbitlaunch --config=/etc/hobbit/clientlaunch.cfg --log=/var/log/hobbit/clientlaunch.log --pidfile=/var/run/hobbit/clientlaunch.pid hobbit 19832 0.0 0.0 4400 696 ?S15:54 0:00 \_ /bin/sh /usr/lib/hobbit/client/bin/hobbitclient.sh hobbit 19842 0.0 0.0 4400 696 ?S15:54 0:00 \_ /bin/sh /usr/lib/hobbit/client/bin/hobbitclient-linux.sh hobbit 19871 0.0 0.0 4400 616 ?S15:54 0:00 \_ sh -c vmstat 300 2 1/var/lib/hobbit/tmp/hobbit_vmstat.hosntame 21; mv /var/lib/hobbit/tmp/hobbit_vmstat.hhostname /var/lib/hobbit/tmp/hobbit_vmstat.hostname hobbit 19873 0.0 0.0 6508 512 ?S15:54 0:00 | \_ vmstat 300 2 hobbit 19872 0.0 0.0 4308 356 ?S15:54 0:00 \_ sleep 5 DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.2 LTS installed xymon-client 4.3.0~beta2.dfsg-9.1ubuntu0.1 Kind regards, Joao ** Affects: xymon (Ubuntu) Importance: Undecided Status: New ** Description changed: + Hi guys + the init file configuration is wrong /etc/init.d/hobbit-client: [ -z $MACHINEDOTS ] MACHINEDOTS=`hostname -f` this is searching for a variable not set and then sets the machine name using hostname -f should be: MACHINEDOTS The hostname of the local system. Default: Taken from uname -n. https://www.xymon.com/xymon/help/manpages/man5/xymonclient.cfg.5.html the reason is that uname -n takes only the name part of hostname and hostname -f takes the fqdn - I've also noticed that every time the init script gets executed it doesn't kill all the processes, there is trash left behind hobbit 19162 0.0 0.0 4400 612 ?S15:53 0:00 sh -c vmstat 300 2 1/var/lib/hobbit/tmp/hobbit_vmstat.hostname-19132 21; mv /var/lib/hobbit/tmp/hobbit_vmstat.ISSV-hostname /var/lib/hobbit/tmp/hobbit_vmstat.hostname hobbit 19164 0.0 0.0 6508 516 ?S15:53 0:00 \_ vmstat 300 2 hobbit 19233 0.0 0.0 4400 616 ?S15:53 0:00 sh -c vmstat 300 2 1/var/lib/hobbit/tmp/hobbit_vmstat.hhostname 21; mv /var/lib/hobbit/tmp/hobbit_vmstat.hhostname /var/lib/hobbit/tmp/hobbit_vmstat.hostname hobbit 19235 0.0 0.0 6508 516 ?S15:53 0:00 \_ vmstat 300 2 hobbit 19831 0.0 0.0 8608 680 ?Ss 15:54 0:00 /usr/lib/hobbit/client/bin/hobbitlaunch --config=/etc/hobbit/clientlaunch.cfg --log=/var/log/hobbit/clientlaunch.log --pidfile=/var/run/hobbit/clientlaunch.pid hobbit 19832 0.0 0.0 4400 696 ?S15:54 0:00 \_ /bin/sh /usr/lib/hobbit/client/bin/hobbitclient.sh hobbit 19842 0.0 0.0 4400 696 ?S15:54 0:00 \_ /bin/sh /usr/lib/hobbit/client/bin/hobbitclient-linux.sh hobbit 19871 0.0 0.0 4400 616 ?S15:54 0:00 \_ sh -c vmstat 300 2 1/var/lib/hobbit/tmp/hobbit_vmstat.hosntame 21; mv /var/lib/hobbit/tmp/hobbit_vmstat.hhostname /var/lib/hobbit/tmp/hobbit_vmstat.hostname hobbit 19873 0.0 0.0 6508 512 ?S15:54 0:00 | \_ vmstat 300 2 hobbit 19872 0.0 0.0 4308 356 ?S15:54 0:00 \_ sleep 5 - DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION=Ubuntu 12.04.2 LTS + installed xymon-client 4.3.0~beta2.dfsg-9.1ubuntu0.1 - installed xymon-client 4.3.0~beta2.dfsg-9.1ubuntu0.1 + + Kind regards, + Joao -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https
[Bug 1343010] [NEW] blcr-dkms 0.8.5-2: blcr kernel module failed to build
Public bug reported: error occurs after boot ProblemType: Package DistroRelease: Ubuntu 13.10 Package: blcr-dkms 0.8.5-2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DKMSKernelVersion: 3.11.0-26-generic Date: Wed Jul 16 23:53:37 2014 DuplicateSignature: dkms:blcr-dkms:0.8.5-2:configure: error: Unable to use kernel 3.11.0-26-generic - unable to determine how to call attach_pid() MarkForUpload: True PackageArchitecture: all PackageVersion: 0.8.5-2 SourcePackage: blcr Title: blcr-dkms 0.8.5-2: blcr kernel module failed to build UpgradeStatus: Upgraded to saucy on 2014-06-02 (44 days ago) ** Affects: blcr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1343010 Title: blcr-dkms 0.8.5-2: blcr kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1343010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181789] Re: second call of 'initctl start' leads to fork instead of exec ('mount: / is busy' during shutdown)
Same here, kubuntu 14.04 64bits on a Dell Precision 390 with nVidia Quadro. No wireless cards. Tried with nouveau nvidia driver and the 313 proprietary driver. Had BIOS version 2.4.0, upgraded to 2.6.0 (thought I had bricked the mobo in the process, as kubuntu did not shutdown as part of the bios upgrade process, so I had to long-press the power button, then the pc wouldn't boot anymore - beep codes, fixed with a BIOS reset, then used a usb live debian wheezy rescue to do the BIOS upgrade). When Booted with a usb pendrive with debian wheezy rescue, it powers off. I have 3 other Precision 390 machines with debian wheezy, and they shutdown correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181789 Title: second call of 'initctl start' leads to fork instead of exec ('mount: / is busy' during shutdown) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1181789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327545] [NEW] blcr-dkms 0.8.5-2: blcr kernel module failed to build
Public bug reported: I get this bug after login ProblemType: Package DistroRelease: Ubuntu 13.10 Package: blcr-dkms ProcVersionSignature: Ubuntu 3.11.0-23.40-generic 3.11.10.10 Uname: Linux 3.11.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DKMSKernelVersion: 3.11.0-23-generic Date: Sat Jun 7 13:27:44 2014 DuplicateSignature: dkms:blcr-dkms:0.8.5-2:configure: error: Unable to use kernel 3.11.0-23-generic - unable to determine how to call attach_pid() MarkForUpload: True PackageArchitecture: all PackageVersion: 0.8.5-2 SourcePackage: blcr Title: blcr-dkms 0.8.5-2: blcr kernel module failed to build UpgradeStatus: Upgraded to saucy on 2014-06-02 (4 days ago) ** Affects: blcr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327545 Title: blcr-dkms 0.8.5-2: blcr kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blcr/+bug/1327545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327546] [NEW] speakup 3.1.5.dfsg.1-1ubuntu1: speakup kernel module failed to build
Public bug reported: after login... ProblemType: Package DistroRelease: Ubuntu 13.10 Package: speakup 3.1.5.dfsg.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-23.40-generic 3.11.10.10 Uname: Linux 3.11.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DKMSKernelVersion: 3.11.0-23-generic Date: Sat Jun 7 13:25:57 2014 DuplicateSignature: dkms:speakup:3.1.5.dfsg.1-1ubuntu1:include/linux/bitops.h:190:2: error: expected identifier or '(' before '{' token MarkForUpload: True PackageArchitecture: all PackageVersion: 3.1.5.dfsg.1-1ubuntu1 SourcePackage: speakup Title: speakup 3.1.5.dfsg.1-1ubuntu1: speakup kernel module failed to build UpgradeStatus: Upgraded to saucy on 2014-06-02 (4 days ago) ** Affects: speakup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327546 Title: speakup 3.1.5.dfsg.1-1ubuntu1: speakup kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speakup/+bug/1327546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325403] VarLogDistupgradeLspcitxt.txt
apport information ** Attachment added: VarLogDistupgradeLspcitxt.txt https://bugs.launchpad.net/bugs/1325403/+attachment/4125608/+files/VarLogDistupgradeLspcitxt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325403 Title: upgrade 13.10 to 14.04 (Muon) -impossivel calcular a actualização da versão To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1325403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325403] VarLogDistupgradeAptlog.txt
apport information ** Attachment added: VarLogDistupgradeAptlog.txt https://bugs.launchpad.net/bugs/1325403/+attachment/4125607/+files/VarLogDistupgradeAptlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325403 Title: upgrade 13.10 to 14.04 (Muon) -impossivel calcular a actualização da versão To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1325403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325403] Re: upgrade 13.10 to 14.04 (Muon) -impossivel calcular a actualização da versão
apport information ** Tags added: apport-collected dist-upgrade saucy ** Description changed: Impossível calcular a actualização da versão. Ocorreu um problema durante o cálculo da actualização. Isto pode ser causado por: * estar a actualizar para uma versão de prá-lançamento de Ubuntu * já ter a versão de pré-lançamento actual * ter pacotes de software não oficiais, que não são fornecidos pelo Ubuntu Se nada disto se aplica, então por favor relate este erro... + --- + ApportVersion: 2.12.5-0ubuntu2.2 + Architecture: amd64 + CrashDB: ubuntu + DistroRelease: Ubuntu 13.10 + MarkForUpload: True + NonfreeKernelModules: nvidia + Package: ubuntu-release-upgrader (not installed) + ProcVersionSignature: Ubuntu 3.11.0-22.38-generic 3.11.10.8 + Tags: saucy dist-upgrade + Uname: Linux 3.11.0-22-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2014-06-02 (2 days ago) + UserGroups: adm admin audio cdrom dialout kismet lpadmin mythtv plugdev pulse pulse-access sambashare video ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1325403/+attachment/4125605/+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/1325403 Title: upgrade 13.10 to 14.04 (Muon) -impossivel calcular a actualização da versão To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1325403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325403] VarLogDistupgradeScreenlog.txt
apport information ** Attachment added: VarLogDistupgradeScreenlog.txt https://bugs.launchpad.net/bugs/1325403/+attachment/4125610/+files/VarLogDistupgradeScreenlog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1325403 Title: upgrade 13.10 to 14.04 (Muon) -impossivel calcular a actualização da versão To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1325403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs