The root problem is, that the /usr/share/applications/k4dirstat.desktop
file has following line:
MimeType=inode/directory;
This line should be removed in order to avoid this problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 20.04.4 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
k4dirstat:
Installed: 3.2.0-1build1
Candidate:
Before marking this as "invalid", please express this in
/etc/default/gpsd - otherwise user's don't understand, that the -G
requires also change into /lib/systemd/system/gpsd.socket file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The solution is to modify file /lib/systemd&/system/gpsd.socket as
follows:
...
#ListenStream=127.0.0.1:2947 <--- comment out this line
ListenStream=0.0.0.0:2947 <--- add this line
...
This works for IPv4, but for IPv6, I did not get it working. Anyway, I
have disabled IPv6 from my
Installation with the same image, to the same virtual machine
configuration, succeeded, when disk was partitioned using default
options i.e. ext4 as file system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
GPSD does not listen to other addresses, i.e. it does not serve clients
on network, even though -G is defined in /etc/default/gpsd.
Netstat output is as follows:
user@mydevice:~ $ netstat -l | grep gps
tcp0 0 localhost:gpsd 0.0.0.0:*
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 18.04.4 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
onedrive:
Installed: 1.1.20170919-2ubuntu2
Public bug reported:
I tried to install 20.04 (preview image, downloaded 9-Feb-2020) from
scratch, under VirtualBox 6.0.16 r135674 (Qt5.6.2). The host system is
Windows 10 64bit, 16 GB RAM.
The instance was given 4GB RAM, 110 GB disk.
On the installation, only mention worth thing was, that I
Also, the ppa:phpmyadmin/ppa does not offer support for xenial. Only for
bionic and eon. Please see below:
sudo apt-get update
...
Reading package lists... Done
W: The repository 'http://ppa.launchpad.net/phpmyadmin/ppa/ubuntu xenial
Release' does not have a Release file.
N: Data from such a
This is because:
kalle@hostname:~$ sudo add-apt-repository ppa:phpmyadmin/ppa
Test packages for Ubuntu, maintained on salsa.debian.org/phpmyadmin-team
Do not use these packages on production! Wait until they are released through
the official ubuntu-channels.
More info:
Should this be still fixed in 16.04's normal repository?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852536
Title:
Warning in ./libraries/sql.lib.php shown, when any table contents are
listed
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 16.04.6 LTS
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
phpmyadmin:
Installed: 4:4.5.4.1-2ubuntu2.1
I noticed that RabbitVCS / checkerservice.py was the reason for hanging.
After I removed the RabbitVCS installation, Nautilus doesn't hang any
more.
Could this bug be moved to rabbitvcs-nautilus?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Ubuntu 18.04.3 LTS
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
nautilus:
Installed: 1:3.26.4-0~ubuntu18.04.4
>> Uname: Linux 2.6.32-042stab128.2 x86_64
> you can't run this ancient kernel in a Xenial release
This is something I (and quite many others) can't do anything, as the
kernel is provided by OpenVZ. When I last time asked the service
provider, they estimated, that it would be on Q2/2019.
>
For Dan:
> then, reboot (so the problem is reproduced) and get the output of
> $ journalctl -b
Attached.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5255102/+files/journalctl.txt
--
You received this bug notification
For Dimitri:
> In addition to debug output from systemd-tmpfiles-setup.service
> as above, it is also interesting to know the permiissions
> on / itself, ie. what's the output of:
> $ ls -la /
kalle@vspk:~$ ls -la /
total 1272
drwxr-xr-x 24 root root4096 Apr 11 15:18 .
drwxr-xr-x 24 root
Yes, tested, and sorry, it did not help. There are still the same errors
in syslog, and /var/run don't have proper directories for sshd etc.
The systemd (etc) version is now as follows:
kalle@vspk:~$ apt-cache policy systemd
systemd:
Installed: 229-4ubuntu21.21+bug1818814v20190411b1
** Attachment added: "find_run_ls_after_reboot.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254877/+files/find_run_ls_after_reboot.txt
** Changed in: systemd (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
>> /var/run directories are not created properly
>what specifically do you mean by this? just that you see log errors?
Following directories were not created automatically, I had to create
them manually in order to enable services to start:
/var/run/fail2ban
/var/run/screen
/var/run/sshd
** Attachment added: "sudo_find_run_ls.txt"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818814/+attachment/5254876/+files/sudo_find_run_ls.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This problem still exists in Ubuntu 16.04 LTS, as for it, the ubuntu-
drivers-common version is 1:0.4.17.7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768637
Title:
/etc/modprobe.d is not a
About var.conf, I wrote that in the initial bug report:
"My first idea was, that for some reason, systemd-tmpfiles was not able to
create the /var directory properly, so I renamed /usr/lib/tmpfiles.d/var.conf
to var.conf, but it was no help."
The output of "ls -lad" is as follows:
Now I tested on the original host. On that machine, update to
229-4ubuntu21.21 did not work - /var/run directories are not created
properly and e.g. OpenSSH server can't start, following is printed on
the log:
Apr 10 13:31:24 vspk systemd[1]: Starting OpenBSD Secure Shell server...
Apr 10
Correction to previous comment: /var/run directories seem to be pretty
much ok now, i.e. openssh starts, but mysql refuses still to start. I'll
try to find out reason for that and get back to here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
The problem still exists in the latest (229-4ubuntu21.21) version.
The grep result is attached as "grep_result.txt" file:
kalle@nxld:~$ grep . /etc/tmpfiles.d/* /run/tmpfiles.d/* /usr/lib/tmpfiles.d/*
> grep_result.txt
grep: /run/tmpfiles.d/*: No such file or directory
** Attachment added:
I got this fixed by manually downgrading packages libsystemd0 and
systemd to versions 229-4ubuntu21.10. I just downloaded those from here:
https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+build/15710450
After rebooting the server, the system works again fine. Anyway, now I
Additional information: the problem appeared after updating
libsystemd0:amd64 from 229-4ubuntu21.10 to 229-4ubuntu21.16
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818814
Title:
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Description:Ubuntu 16.04.6 LTS
Release:16.04
Just an update - this problem still exists in Ubuntu 16.04.3 LTS.
In case someone gets to this page due to this problem, there is a
workaround. Downside on this workaround is, that all network interface
names are then changed to eth0, eth1, eth2 etc, so one must change
settings on the
Just reporting, that this bug still exists in 16.04.3 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1246347
Title:
Lots of "error on subcontainer ‘ia_addr’ insert (-1)" reports in
As i mentioned in the comment #5:
"This was just one of attempts. I tried also the Ubuntu command-line install
method with no updates during the installation. This reported installation
attempt was using the Lubuntu live image, because this way it was easiest to
create the error report."
-->
One note more: Ubuntu has two kinds of installer images: those, which
should be (and so far have been) capable of installing the system
without any network connection, and those, which rely on network
connection to fetch necessary drivers, utilities etc. Now it seems, that
the offline installer
Philip - you need to explain, how and why network problems would effect
this problem. This is particularly because I selected, that updates are NOT
downloaded during installation.
24.5.2017 18.51 "Phillip Susi" kirjoitti:
> You are still having network problems:
>
> Failed to
I assume the problem is here:
---8<---8<---
May 24 11:20:39 lubuntu ubiquity: Reading package lists...
May 24 11:20:39 lubuntu ubiquity:
May 24 11:20:39 lubuntu ubiquity: Building dependency tree...
May 24 11:20:39 lubuntu ubiquity:
May 24 11:20:39 lubuntu ubiquity: Reading state information...
Attached is syslog from another installation attempt, to another (DFI
EC-200) computer. The result was the same, GRUB writing failed.
** Attachment added: "syslog from another attempt"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1690767/+attachment/4882596/+files/syslog
**
I just tested this with Ubuntu 16.04 (amd64) server installation media.
GRUB was written succesfully, so this problem has been introduced after
16.04.
** Changed in: grub-installer (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of
This was just one of attempts. I tried also the Ubuntu command-line install
method with no updates during the installation. This reported installation
attempt was using the Lubuntu live image, because this way it was easiest
to create the error report.
Conclusion: network issues are not part of
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1690767/+attachment/4876780/+files/dmesg.txgt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1690767/+attachment/4876796/+files/syslog.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1690767
Public bug reported:
Computer type is DFI EC700-BT4051-E454.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 17.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
Not known - system is
Public bug reported:
Background information:
Software Center works properly, if launched from computer's own display, but if
it is launched through X2Go's remote connection, it fails to launch. Xfce4 is
used as windowing environment.
1) The release of Ubuntu you are using, via 'lsb_release
This problem exists also in Ubuntu 16.10, which has kernel version
4.8.0-32-generic x86_64.
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is printout from lspci:
---8<---8<---
kalle@backup:/etc/default$ lspci
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
00:01.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Description:Ubuntu Yakkety Yak (development branch)
Release:16.10
beta2 version, downloaded 5-Oct-2016
Please note, this is 32-bit version and is was installed under
** 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/1622877
Title:
MTU probing does not work
To manage notifications about this bug go to:
The bug exists still with kernel version: 4.8.0-040800rc6-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622877
Title:
MTU probing does not work
To manage notifications about this bug go
** Description changed:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 16.04.1 LTS
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
Kernel version 4.4.0-36
3) What
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 16.04.1 LTS
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center
Kernel version 4.4.0-36
3) What you expected to happen
Public bug reported:
The Zabbix 2.4 is installed from standard Ubuntu repositories, on top of
MariaDB.
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
Ubuntu 16.04.1 LTS
2) The version of the package you are using, via 'apt-cache policy
pkgname' or by
This feature worked well in my earlier installation (16.04LTS), but when
I re-installed the system yesterday, adding an alias to my USB network
adapter didn't work any more.
---8<---8<---
$ sudo ifup enx0016:0
RTNETLINK answers: Numerical result out of range
Failed to bring up
I came to comment here, as I reported the same bug and it was marked as
duplicate, which it was.
Anyway, only after reporting the bug I noticed, that Zabbix itself
tells, that it is not compatible with PHP7. Thus the whole Zabbix
package should be withdrawn from Ubuntu 16.04 until it supports
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System ->
About Ubuntu
Ubuntu 16.04 LTS
2) The version of the package you are using, via 'apt-cache policy pkgname' or
by checking in Software Center
zabbix-frontend-php:
Installed: 1:2.4.7+dfsg-2ubuntu2
I'm trying to set the package to zabbix-frontend-php, but this system
doesn't let me to change it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1581926
Title:
Zabbix PHP front-end, fatal error,
Public bug reported:
The complete error message is as follows:
./testapp: relocation error: ./testapp: symbol __get_cpu_features, version
GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
The "testapp" has been compiled in Ubuntu 14.04 LTS server with Free
Pascal to 64bit
** Tags added: utopic vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404880
Title:
usbip doesn't work, missing kernel modules
To manage notifications about this bug go to:
This error exists also in 15.04 (x86-64).
Error message is as follows:
---8---8---
user@usbtest:~$ sudo usbipd
usbip err: stub_driver.c: 33 (open_sysfs_stub_driver) usbip_common_mod.ko and
usbip.ko must be loaded
** (process:1226): ERROR **: driver open failed
---8---8---
--
You received
This error exists still in 14.10. Tested with media
lubuntu-14.10-desktop-i386.iso, installed under VirtualBox 4.3.22
r98236, host OS is 64bit MS Windows 7 Pro SP1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I just made a clean 11.10 install using alternate i386 install CD. I
installed system with static IP address and performed full update.
Everything was fine. After rebooting the system first time,
/etc/resolv.conf was wiped clean.
This means that the error correction has not been distributed yet
Replying to myself (and maybe others having the same problem):
workaround for this error is to forcibly write protect the
/etc/resolv.conf file with following command:
sudo chattr +i /etc/resolv.conf
This prevents NetworkManager from overwriting the file.
--
You received this bug notification
Public bug reported:
I updated several computers from Ubuntu 11.04 to 11.10. In all of these
computers, /etc/resolv.conf was manually maintained. All of these
computers are having static IPs.
After the update was finished and computer(s) had rebooted, resolv.conf
had been cleared and had only
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/875949
Title:
resolv.conf is cleared at system reset
To manage notifications about this bug go to:
It seems to say
modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified]
in the error information. It is because I have tried to solve the
problem by following instructions from several places with this one
computer, no luck. Rest of computers are waiting that I'll get the
problem
Not 100% related to this error, but I tried Unity as a workaround
solution in my desktop computer. Unity worked even worse than Gnome so
it really can't be relied on.
On Tue, Oct 26, 2010 at 2:53 AM, Joaquin jknv...@gmail.com wrote:
I don't know why to use Unity!
Unity is for netbooks!
I don't
--
[i865] GPU lockup d5938c62 (PGTBL_ER: 0x0029)
https://bugs.launchpad.net/bugs/664969
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: xserver-xorg-video-intel
I was using the ubuntu 10.10 live CD and got the error message before I
had even started to experiment the system.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: xserver-xorg-video-intel 2:2.12.0-1ubuntu5
Even when the theme has been changed to another one and the panel is
once corrected, items may still disappear from the panel. For example,
the shutdown item disappears quite often from my panel after I have
used the computer for a while.
--
Visual corruption affecting several panel applets
I just upgraded my distribution to Maverick and the error still exists.
--
Panel utilities not shown on startup using Matrox gfx with compiz
https://bugs.launchpad.net/bugs/572550
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Today morning I executed the apt-get update; apt-get upgrade and after
rebooting the computer, audio started to work. I did not monitor, what
packages were updated, sorry.
So from my point of view, the error does not exist any more and it could
be closed.
--
No audio in Samsung Q330 after
Public bug reported:
Binary package hint: gnome-panel
1) Ubuntu 10.10 release candidate
2) 1:2.30-2.1ubuntu3
3) The poweroff/logout/etc symbol should be shown at the rightmost symbol on
the top panel
4) The poweroff/logout/etc symbol is not shown on the top panel. Changing the
desktop theme
** Attachment added: Screen dump of top panel area
https://bugs.launchpad.net/bugs/656723/+attachment/1678471/+files/Screenshot.png
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/656723/+attachment/1678472/+files/Dependencies.txt
--
Poweroff/logout/etc not shown
Additional information: Similar error, about panel utilities not shown,
has appeared also on 10.04 version of Ubuntu. I have noticed it on
computer with Matrox display adapter. The error ID for that error is
#572550.
--
Poweroff/logout/etc not shown on panel
apport information
** Description changed:
I installed Maverick (29-Sep-2010 version) to Samsung Q330 laptop using
32-bit alternate installation CD. The computer has 4 gigabytes of memory
and it is capable of running 64 bit software.
When I started the system for the first time after
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669231/+files/CurrentDmesg.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: Dependencies.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669232/+files/Dependencies.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: GdmLog.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669233/+files/GdmLog.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: GdmLog1.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669234/+files/GdmLog1.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: GdmLog2.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669235/+files/GdmLog2.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: Lspci.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669236/+files/Lspci.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification because
apport information
** Attachment added: Lsusb.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669237/+files/Lsusb.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification because
apport information
** Attachment added: PciDisplay.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669238/+files/PciDisplay.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669239/+files/ProcCpuinfo.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669240/+files/ProcInterrupts.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: ProcModules.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669241/+files/ProcModules.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669242/+files/RelatedPackageVersions.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You
apport information
** Attachment added: UdevDb.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669243/+files/UdevDb.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: UdevLog.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669244/+files/UdevLog.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: XorgLog.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669245/+files/XorgLog.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: XorgLogOld.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669246/+files/XorgLogOld.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: Xrandr.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669247/+files/Xrandr.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: setxkbmap.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669249/+files/setxkbmap.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: peripherals.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669248/+files/peripherals.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug
apport information
** Attachment added: xdpyinfo.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669250/+files/xdpyinfo.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
apport information
** Attachment added: xkbcomp.txt
https://bugs.edge.launchpad.net/bugs/653602/+attachment/1669251/+files/xkbcomp.txt
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
You received this bug notification
Public bug reported:
I installed Maverick (29-Sep-2010 version) using 32-bit alternate
install CD to Samsung Q330 laptop having actually 64 bit processor and 4
gigabytes of memory.
The installation itself went fine. After Ubuntu login screen appeared
and I typed in my credentials, there were no
Public bug reported:
I installed Maverick (29-Sep-2010 version) to Samsung Q330 laptop using
32-bit alternate installation CD. The computer has 4 gigabytes of memory
and it is capable of running 64 bit software.
When I started the system for the first time after installation and
entered my
The ISO file was valid, here is output of MD5SUM checking:
---8---8---
$ md5sum -c MD5SUMS.txt
md5sum: ubuntu-10.10-rc-alternate-amd64.iso: No such file or directory
ubuntu-10.10-rc-alternate-amd64.iso: FAILED open or read
ubuntu-10.10-rc-alternate-i386.iso: OK
md5sum:
MD5SUM check was executed for the ISO file, it passed OK.
I also executed the integrity check (check disk for defects) on the
alternate disk boot main menu, it also passed OK.
--
Restricted video driver for Samsung Q330 / Nvidia does not work in Maverick
https://bugs.launchpad.net/bugs/653602
Here is more information about the device:
---8---8---
$ lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port
(rev 02)
00:02.0 VGA compatible controller: Intel Corporation Core
Here is more information about the device:
---8---8---
output of lspci -v , audio device part:
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High
Definition Audio (rev 05)
Subsystem: Samsung Electronics Co Ltd Device c557
Flags: bus master, fast devsel,
1 - 100 of 148 matches
Mail list logo